docs: MCP docs and comments disagree with the wire behavior
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
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:155sayslegacy-omitted-versionnegotiates2025-03-26. The transcript andlegacyOmittedVersionCoercion(test/wireoracle/scenarios.go:408) say2025-11-25.- The
registerToolscomment (internal/mcp/server.go:615-617) says registration order sets thetools/listorder. go-sdk sorts tools by name. docs/MCP-2026-07-28-SCOPING.md:48says "codegraph_exploreis always registered first".test/integration/mcp_stdout_purity_test.go:66says "codegraph_exploreis 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
- Dominant language
- Go
- Stars
- 0
- Forks
- 0
- Avg merge
- 5h 16m
- Merged PRs (30d)
- 107
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from seanb4t/codegraph-go
-
area:indexer bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
seanb4t/codegraph-go#385 ·
Maintainers usually reply within 1 day
-
chore needs-triage
Difficulty 1/5 Under an hour Newbie friendliness 88/100
seanb4t/codegraph-go#380 ·
Maintainers usually reply within 1 day
-
chore needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
seanb4t/codegraph-go#379 ·
Maintainers usually reply within 1 day
-
chore needs-triage
Difficulty 1/5 1-3 hours Newbie friendliness 84/100
seanb4t/codegraph-go#362 ·
Maintainers usually reply within 1 day
-
area:query bug priority:low spec-needed
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
seanb4t/codegraph-go#355 ·
Maintainers usually reply within 1 day
All issues in seanb4t/codegraph-go
Similar issues
-
enhancement exporter/awskinesis needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
open-telemetry/opentelemetry-collector-contrib#53334 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
erigontech/erigon#26523 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 83/100
SocialGouv/iterion#3376 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
seaweedfs/seaweedfs#12740 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day