You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
README: semantic_query is not a tool, the tool count is 14 not 15, and the team artifact is not written by default #1297
semantic_query exists only as a parameter of search_graph. The README's own MCP Tools table does not list it, so the two sections contradict each other.
2. Tool count is 14, not 15
The intro and the Manual MCP Configuration section both state 15 tools ("you should see codebase-memory-mcp with 15 tools"). The server advertises 14 via tools/list (paginated: 8 with nextCursor: 8, then 6).
3. The team-shared artifact is opt-in, not automatic
Team-Shared Graph Artifact says:
When you index, the artifact is written or refreshed
In practice persistence defaults to false (src/mcp/mcp.c:376), so index_repository reports artifact_present: false and no .codebase-memory/graph.db.zst is created unless persistence: true is passed explicitly.
4. The dead-code Cypher example is rejected by the engine
Supported Cypher offers WHERE NOT EXISTS { (f)<-[:CALLS]-() } as the dead-code example. The engine rejects the inbound form. See #1293.
Thanks for checking the README against the actual server rather than relying on the prose.
The contradictions remain code-grounded on current main: semantic_query is a search_graph parameter in the tool schema (src/mcp/mcp.c:381-416), and persistence is explicitly default false (src/mcp/mcp.c:376). The server advertises the TOOLS array beginning at src/mcp/mcp.c:347, not a standalone semantic_query tool.
PR #1315 is now linked to this documentation bug and is queued for review. I have routed the issue to 0.9.1-rc at priority/normal; that routing does not pre-approve the PR. Thank you for grouping the four concrete claims in one reproducible report.
Activity
DeusData commentedon Jul 28, 2026
Thanks for checking the README against the actual server rather than relying on the prose.
The contradictions remain code-grounded on current main: semantic_query is a search_graph parameter in the tool schema (src/mcp/mcp.c:381-416), and persistence is explicitly default false (src/mcp/mcp.c:376). The server advertises the TOOLS array beginning at src/mcp/mcp.c:347, not a standalone semantic_query tool.
PR #1315 is now linked to this documentation bug and is queued for review. I have routed the issue to 0.9.1-rc at priority/normal; that routing does not pre-approve the PR. Thank you for grouping the four concrete claims in one reproducible report.
mindplay-dk commentedon Aug 17, 2026
Also, the readme mentions
trace_call_path, which is actually calledtrace_path.And there's an undocumented
check_index_coveragetool as well.Maybe ask your agent to check if the documentation matches the codebase? 😊
docs: MCP tool count is 17; document the three missing tools
docs: MCP tool count is 17; document the three missing tools
docs: MCP tool count is 17; document the three missing tools
Merge pull request #2403 from DeusData/fix/issue-1297
docs(readme): semantic_query is a search_graph parameter; team artifa…
DeusData commentedon Sep 30, 2026
Thank you again for reporting this, @melihemreguler! The fix is now on
mainin 39da5de (merged via #2403), and it will ship in the next release.