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 <samthanawalla@google.com>
TryBot-Bypass: Jonathan Amsterdam <jba@google.com>
Commit-Queue: Jonathan Amsterdam <jba@google.com>
This commit is contained in:
Jonathan Amsterdam 2025-05-14 13:10:57 -04:00
commit 0e7f052616

View file

@ -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. their signatures all share this form.
We do this, rather than providing more convenient shortcut signatures, We do this, rather than providing more convenient shortcut signatures,
to maintain backward compatibility if the spec makes backward-compatible changes 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 To avoid boilerplate, we don't repeat this
signature for RPCs defined in the spec; readers may assume it when we mention a signature for RPCs defined in the spec; readers may assume it when we mention a
"spec method." "spec method."