docs/client: fix the SEP-1034 and SEP-1330 links (#1252)

The "Schema defaults and enums" section of docs/client.md links SEP-1034
to https://modelcontextprotocol.io/seps/1034 and SEP-1330 to
https://modelcontextprotocol.io/seps/1330, and both of those bare-number
URLs are dead. modelcontextprotocol.io serves SEPs at number-plus-slug
URLs, which is what every other SEP link in this repo already uses
(seps/2575-stateless-mcp,
seps/2577-deprecate-roots-sampling-and-logging,
seps/2596-feature-lifecycle-and-deprecation-policy,
seps/2207-oidc-refresh-token-guidance); these two were the only
bare-number ones left. I took the replacement slugs from the site's own
sitemap.xml, so the `1034--` double hyphen is what is published rather
than a typo here.

curl -sIL on the two old URLs returns 404 and 404, and on the two new
ones 200 and 200. The edit is in internal/docs/client.src.md with
docs/client.md regenerated by `go generate ./internal/docs`, and `go
build ./... && go test ./...` pass.

Co-authored-by: Guglielmo Colombo <guglielmoc@google.com>
This commit is contained in:
rishabh 2026-09-14 13:20:25 -04:00 • committed by GitHub
commit 0c0eb23625
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 4 additions and 4 deletions

View file

@ -304,7 +304,7 @@ func Example_elicitation() {
`ElicitParams.RequestedSchema` is a flat schema of primitive fields, which the `ElicitParams.RequestedSchema` is a flat schema of primitive fields, which the
client renders as a form. Two field keywords shape that form. client renders as a form. Two field keywords shape that form.
A `Default` ([SEP-1034](https://modelcontextprotocol.io/seps/1034)) prefills a A `Default` ([SEP-1034](https://modelcontextprotocol.io/seps/1034--support-default-values-for-all-primitive-types-in)) prefills a
field. When the user accepts without supplying it, the SDK fills the field in field. When the user accepts without supplying it, the SDK fills the field in
from the schema before the result reaches either side's caller — the client from the schema before the result reaches either side's caller — the client
does so after its elicitation handler returns, and `ServerSession.Elicit` does does so after its elicitation handler returns, and `ServerSession.Elicit` does
@ -313,7 +313,7 @@ defaulted field `Required` defeats it: accepted content is validated against
the schema before defaults are applied, so an answer that omits the field is the schema before defaults are applied, so an answer that omits the field is
rejected rather than defaulted. rejected rather than defaulted.
An `Enum` ([SEP-1330](https://modelcontextprotocol.io/seps/1330)) restricts a An `Enum` ([SEP-1330](https://modelcontextprotocol.io/seps/1330-elicitation-enum-schema-improvements-and-standards)) restricts a
field to a fixed set of values, which the client renders as a choice. Enums field to a fixed set of values, which the client renders as a choice. Enums
are supported only on `"string"` fields; declaring one on another type is are supported only on `"string"` fields; declaring one on another type is
rejected. To label the choices, set the legacy `enumNames` keyword through rejected. To label the choices, set the legacy `enumNames` keyword through

View file

@ -99,7 +99,7 @@ pattern.
`ElicitParams.RequestedSchema` is a flat schema of primitive fields, which the `ElicitParams.RequestedSchema` is a flat schema of primitive fields, which the
client renders as a form. Two field keywords shape that form. client renders as a form. Two field keywords shape that form.
A `Default` ([SEP-1034](https://modelcontextprotocol.io/seps/1034)) prefills a A `Default` ([SEP-1034](https://modelcontextprotocol.io/seps/1034--support-default-values-for-all-primitive-types-in)) prefills a
field. When the user accepts without supplying it, the SDK fills the field in field. When the user accepts without supplying it, the SDK fills the field in
from the schema before the result reaches either side's caller — the client from the schema before the result reaches either side's caller — the client
does so after its elicitation handler returns, and `ServerSession.Elicit` does does so after its elicitation handler returns, and `ServerSession.Elicit` does
@ -108,7 +108,7 @@ defaulted field `Required` defeats it: accepted content is validated against
the schema before defaults are applied, so an answer that omits the field is the schema before defaults are applied, so an answer that omits the field is
rejected rather than defaulted. rejected rather than defaulted.
An `Enum` ([SEP-1330](https://modelcontextprotocol.io/seps/1330)) restricts a An `Enum` ([SEP-1330](https://modelcontextprotocol.io/seps/1330-elicitation-enum-schema-improvements-and-standards)) restricts a
field to a fixed set of values, which the client renders as a choice. Enums field to a fixed set of values, which the client renders as a choice. Enums
are supported only on `"string"` fields; declaring one on another type is are supported only on `"string"` fields; declaring one on another type is
rejected. To label the choices, set the legacy `enumNames` keyword through rejected. To label the choices, set the legacy `enumNames` keyword through