Catch documentation that lies about your code. Checks docs' claims against the source and fails CI when they drift. Also runs as an MCP tool for coding agents.
Docverity exposes 3 tools via MCP. All have descriptions (10-50 chars), but schemas are incomplete or inferred. The 'check' tool has a detailed input schema with 7 parameters (docs, root, llm, model, coverage, failConfidence, failOn, strict, format), but output schema is undocumented. The 'suggest' tool has 4 parameters with descriptions but no type definitions visible in the source. The 'mcp' tool has an empty input schema. Parameter descriptions are present but terse (10-30 chars), below the 72-char baseline. No error handling guidance, no output schema documentation, and tool definitions appear inferred from CLI argument parsing rather than explicit MCP registration. Naming is verb-based (check, suggest, mcp) but generic; 'mcp' is not action-oriented.
Check docs for claims that no longer match the code.
Run as an MCP server (stdio) so agents can check docs as a tool.
Draft documentation for everything the code exposes but the docs don't cover.
Tool 'mcp' has empty input schema and generic name. 'mcp' does not convey action (verb_noun pattern). Should be 'run_as_server' or similar. Empty schema means LLM cannot infer parameters.
Output schemas undocumented for all tools. LLMs cannot plan downstream calls or extract results without knowing return structure. 'check' should document success/failure format, findings array, exit code.
Parameter descriptions are terse (10-30 chars, below 72-char baseline). E.g., 'repo root' lacks context on what 'root' means (filesystem path? git root?). 'llm' is ambiguous, skip LLM or use LLM?
No error handling guidance. If 'check' fails (e.g., docs not found, LLM API error), the tool returns nothing actionable. Should guide LLM: 'Docs not found in root. Ensure README.md or docs/ exists.'
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 40 | 2026-07-28+ | v2 |
Tool definitions inferred from CLI parsing, not explicit MCP registration visible in source. Cannot confirm tool names, schemas, and descriptions are formally registered with the MCP SDK.