From 392e47ea29f78785c09fd1f30b20d5115b22af42 Mon Sep 17 00:00:00 2001
From: Copilot <198982749+Copilot@users.noreply.github.com>
Date: Tue, 17 Feb 2026 09:30:11 -0500
Subject: [PATCH] Document https:// direct-fetch provision in
 ReadResourceRequestParams (#1296)

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: stephentoub <2642209+stephentoub@users.noreply.github.com>
---
 .../Protocol/ReadResourceRequestParams.cs              | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/src/ModelContextProtocol.Core/Protocol/ReadResourceRequestParams.cs b/src/ModelContextProtocol.Core/Protocol/ReadResourceRequestParams.cs
index 12b752a..6d358e9 100644
--- a/src/ModelContextProtocol.Core/Protocol/ReadResourceRequestParams.cs
+++ b/src/ModelContextProtocol.Core/Protocol/ReadResourceRequestParams.cs
@@ -7,8 +7,18 @@ namespace ModelContextProtocol.Protocol;
 /// 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="https://github.com/modelcontextprotocol/specification/blob/main/schema/">schema</see> for details.
+/// </para>
 /// </remarks>
 public sealed class ReadResourceRequestParams : RequestParams
 {