Skip to main content
Glama
Sign In
verdoc-mcp

verdoc-mcp

by verdochello
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

verdoc_scan

Analyze a public GitHub repository to get structured facts about toolchain commands, directory layout, language split, CI presence, documentation health score, and phantom paths missing from the repository.

Instructions

Structured facts about a public GitHub repository: toolchain commands with the manifest each was quoted from, directory layout, language split, CI and test presence, a 0-100 documentation-health score, and phantom_paths - paths the README cites that do not exist in the git tree. Deterministic; no language model. Costs $0.01 in USDC.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "repo": "<repo>"
    },
    "name": "verdoc_scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoYesPublic GitHub repository as owner/name, or a github.com URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description discloses determinism, cost, and the public repo constraint. It doesn't discuss failure modes, auth, or rate limits, but for a read-only public scan the disclosed traits are reasonably reassuring. Lacks deeper behavioral nuance like output structure edge cases.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single, information-dense sentence that packs all key details—output fields, determinism, and cost—without redundant wording. Front-loaded with the primary purpose, making it easy to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description thoroughly enumerates expected return contents (toolchain commands, phantom_paths, etc.) and adds determinism/cost context. It doesn't describe exact data structures, but that is acceptable for a fact-collection tool. The single parameter and input schema are fully covered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% for the single 'repo' parameter, explicitly defining it as a GitHub 'owner/name' or URL. The description adds no new parameter details, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear action and resource: 'Structured facts about a public GitHub repository' with a detailed list of content types. It distinguishes itself by highlighting deterministic, non-LLM behavior and cost, setting it apart from a typical analysis tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for deterministic repository analysis, noting 'Deterninistic; no language model' and cost. However, it does not explicitly mention when to use it over the sibling tool verdoc_agents_md, nor any exclusions or prerequisites beyond 'public GitHub repository'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools