docs: MCP docs and comments disagree with the wire behavior

Open Beginner friendly
#132 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
go, markdown
Domain
documentation

Research direction

Four stale comments need rewording, not code changes: the negotiated version in test/wireoracle/COVERAGE-BASELINE.md:155, the registerTools comment in internal/mcp/server.go:615-617, and the tool-order claims in docs/MCP-2026-07-28-SCOPING.md:48 and test/integration/mcp_stdout_purity_test.go:66. Check each against the transcript and legacyOmittedVersionCoercion in test/wireoracle/scenarios.go:408, and confirm that the tools/list order is sorted by name. Done when the four passages match the pinned behavior and no test or transcript file has changed.

Written by the indexing model from the issue text.

Description

area:mcp documentation priority:low
What's wrong

Four passages describe MCP behavior that the wire transcripts contradict. The transcripts and tests are right. Only the prose is stale.

  • test/wireoracle/COVERAGE-BASELINE.md:155 says legacy-omitted-version negotiates 2025-03-26. The transcript and legacyOmittedVersionCoercion (test/wireoracle/scenarios.go:408) say 2025-11-25.
  • The registerTools comment (internal/mcp/server.go:615-617) says registration order sets the tools/list order. go-sdk sorts tools by name.
  • docs/MCP-2026-07-28-SCOPING.md:48 says "codegraph_explore is always registered first".
  • test/integration/mcp_stdout_purity_test.go:66 says "codegraph_explore is the only tool visible with no allowlist entry". All eight tools register by default.
Acceptance criteria
  • Each passage matches the behavior the transcripts pin.
  • No test or transcript changes.

🤖 Generated with Claude Code

https://claude.ai/code/session_01UNqdnC3q6U362BvyfxuKCF

Dominant language
Go
Stars
0
Forks
0
Avg merge
5h 16m
Merged PRs (30d)
107

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from seanb4t/codegraph-go

All issues in seanb4t/codegraph-go

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.