Context

Spec commit df1152e297eca7afb2ef4f5aecd8f6b52177ac6a (merged via PR #802) added a clarification to the "Reading Resources" section of the spec: if the resource URI uses the https:// scheme, clients may fetch the resource directly from the web instead of going through resources/read. This was already documented in the "Common URI Schemes" section but the PR makes it more discoverable.

What to change

Update the XML doc comments on ReadResourceRequestParams in src/ModelContextProtocol.Core/Protocol/ReadResourceRequestParams.cs to mention the https:// direct-fetch provision.

Current

/// <summary>
/// Represents the parameters used with a <see cref="RequestMethods.ResourcesRead"/> request from a client to get a resource provided by a server.
/// </summary>
/// <remarks>
/// The server will respond with a <see cref="ReadResourceResult"/> containing the resulting resource data.
/// See the <see href="proxy.php?url=https://github.com/modelcontextprotocol/specification/blob/main/schema/">schema</see> for details.
/// </remarks>
public sealed class ReadResourceRequestParams : RequestParams

Proposed

/// <summary>
/// Represents the parameters used with a <see cref="RequestMethods.ResourcesRead"/> request from a client to get a resource provided by a server.
/// </summary>
/// <remarks>
/// <para>
/// The server will respond with a <see cref="ReadResourceResult"/> containing the resulting resource data.
/// </para>
/// <para>
/// Alternatively, if the resource URI uses the <c>https://</c> scheme, clients may fetch the resource
/// directly from the web instead of using <see cref="RequestMethods.ResourcesRead"/>.
/// Servers should only use the <c>https://</c> scheme when the client is able to fetch and load the
/// resource directly on its own.
/// </para>
/// <para>
/// See the <see href="proxy.php?url=https://github.com/modelcontextprotocol/specification/blob/main/schema/">schema</see> for details.
/// </para>
/// </remarks>
public sealed class ReadResourceRequestParams : RequestParams

No functional or behavioral changes are needed — this is purely a documentation update.