Loading ToolBench

Reading the current corpus…

go-indexer-mcp MCP server · F · ToolBench

go-indexer-mcp

MCP server that indexes Go codebases. It parses Go source files and extracts symbols (functions, types, constants, variables) with their line ranges to provide codebase maps for AI assistants.

2026-07-28+STDIO1 tools

40/100

Definition Quality45

Protocol Readiness50

Supportability26

Spec posture

Inferred effective spec 2026-07-28+·current baseline 2026-07-28

Static source inference · medium confidence

Current-spec patterns detected

Summary

Single-tool server with a moderately well-named tool ('index') but significant gaps in description detail, parameter descriptions, and output schema documentation. The tool name lacks a clear action verb prefix and describes a specialized code indexing function. Parameter descriptions exist but are generic. No explicit output schema is documented in the code. Error handling guidance is absent. The server handles a narrow, domain-specific use case (Go codebase indexing) but lacks the polish and completeness expected of production-grade tools.

Tools (1)

indexread onlysource verified45/100

Index a Go codebase and return a compact listing of all symbols (functions, types, consts, vars) with their line ranges.

Issues (6)

HIGHtool ↗

Tool name 'index' does not start with a clear action verb. Convention suggests 'index_codebase', 'analyze_go_package', or 'list_symbols' to clarify intent for LLMs.

index

HIGHtool ↗

Output schema not explicitly documented. The tool returns a JSON object with PackageIndex structure (nested FileIndex/Symbol objects with named fields), but no schema definition is visible in the MCP tool registration. LLMs cannot plan downstream tool calls or extract fields reliably without knowing the response shape.

index

MEDIUMtool-description ↗

Parameter 'filter' description is vague ('Optional path filter to show only a specific package (directory) or file') and lacks format guidance. Should specify: 'relative path prefix (e.g., 'cmd/main', 'internal/auth'); matching is case-sensitive; use forward slashes'.

index

MEDIUMtool-description ↗

Parameter 'path' description does not document behavior when directory does not exist, contains no Go files, or has parse errors. No guidance on what constitutes 'success' or how failures are reported.

Recommendations

Rename tool to 'index_go_codebase' or 'analyze_go_package' to clearly signal the action (indexing/analyzing) and domain (Go code).
Document the complete output schema in the tool description or as a separate schema field. Example: 'Returns PackageIndex object with keys: path (string), dir (string), files (array of FileIndex). Each FileIndex contains: path, imports (array of strings), symbols (array of Symbol objects with name, kind, receiver, type_kind, signature, start_line, end_line, doc_head).'
Expand the 'path' parameter description: 'Directory path to index (absolute or relative). Defaults to current working directory if not specified or empty string. Must be a readable directory; returns error if path does not exist or is not accessible.'
Expand the 'filter' parameter description: 'Optional relative path prefix to filter results (case-sensitive, use forward slashes). Examples: "cmd" shows cmd/*.go and cmd/**/*.go; "internal/auth" shows only files under internal/auth/. Empty string disables filter.'
Add error handling guidance to the tool description: 'If directory contains unparseable Go files, those files are skipped with no error. If path is invalid or inaccessible, returns error: "path not accessible: <reason>". For very large codebases (10000+ files), performance may degrade; consider using filter parameter.'
Add per-parameter validation hints: 'path must be a directory (not a file); filter must be a valid relative path (no ../ or absolute paths; regex patterns not supported).'

Score history

Overall score trend

↓ 5 points across a rubric change (v1 → v2)

40/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-22	F	40	2026-07-28+	v2
2026-03-09	F	45	-	v1