René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Reconsider PR #850: Wrong Fix for a Potentially Invalid Use Case","articleBody":"**References:** PR #850, Issue #260\n\n### Rationale 1: `charset=utf-8` is non-conformant\n\n[RFC 8259 §8.1](https://datatracker.ietf.org/doc/html/rfc8259#section-11) and [IANA](https://www.iana.org/assignments/media-types/application/json) do not recognize `charset` as a valid parameter for `application/json`.\n\nThis might result in status 415 with strict servers.\n[csharp-sdk issue](https://github.com/modelcontextprotocol/csharp-sdk/issues/1527)\n\n### Rationale 2: Non-ASCII tool names are spec-violating\n\nThe [MCP spec](https://modelcontextprotocol.io/specification/2025-11-25/server/tools) and accepted [SEP-986](https://github.com/modelcontextprotocol/modelcontextprotocol/issues/986) both restrict tool names to `[a-zA-Z0-9_\\-.]`. Non-ASCII characters like `天気予報` are outside this set (`SHOULD`, not `MUST` — but still discouraged).\n\n\n### Proposed Actions\n1. Revert `Content-Type` header change\n2. Add tool name validation at registration\n\nHappy to submit a PR if maintainers agree.\n\n@Kehrlann ","author":{"url":"https://github.com/jayaraman-venkatesan","@type":"Person","name":"jayaraman-venkatesan"},"datePublished":"2026-04-21T17:18:27.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/929/java-sdk/issues/929"}