From 0e7f0526160c414292b55c008b1527d6081675f7 Mon Sep 17 00:00:00 2001 From: Jonathan Amsterdam Date: Wed, 14 May 2025 13:10:57 -0400 Subject: [PATCH] internal/mcp: design.md: link to spec change Add a link to a recent commit that illustrates a backward-compatible change. Change-Id: I5e277f9417cf9bbbc5146512e29a3cb8205a4e14 Reviewed-on: https://go-review.googlesource.com/c/tools/+/672716 Reviewed-by: Sam Thanawalla TryBot-Bypass: Jonathan Amsterdam Commit-Queue: Jonathan Amsterdam --- design/design.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/design/design.md b/design/design.md index 7d069f1..3185f87 100644 --- a/design/design.md +++ b/design/design.md @@ -495,7 +495,9 @@ Our SDK has a method for every RPC in the spec, and except for `CallTool`, their signatures all share this form. We do this, rather than providing more convenient shortcut signatures, to maintain backward compatibility if the spec makes backward-compatible changes -such as adding a new property to the request parameters. +such as adding a new property to the request parameters +(as in [this commit](https://github.com/modelcontextprotocol/modelcontextprotocol/commit/2fce8a077688bf8011e80af06348b8fe1dae08ac), +for example). To avoid boilerplate, we don't repeat this signature for RPCs defined in the spec; readers may assume it when we mention a "spec method."