Skip to main content
Glama

docs-list_repo_docs

List markdown documents under a sibling repo's docs directory while excluding ADR files. Use it to discover documentation files available for reading in a specified Exeris repo.

Instructions

List markdown documents under <repo>/docs/** for an Exeris sibling repo. The adr/ subdirectory is excluded — those are the registry's territory and reachable via docs-list_adrs / docs-get_adr. Use docs-list_repos to discover valid repo names.

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": "docs-list_repo_docs"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoYesRepo name (e.g. 'exeris-kernel'). Must match /^exeris-[a-z0-9][a-z0-9-]*$/.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

A4.6/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full behavioral burden; it discloses the recursive glob semantics (`docs/**`), the scope exclusion, and where excluded content lives instead. It does not describe the return shape (paths vs objects) or whether results are truncated/paginated, which are the remaining disclosures an unannotated list tool would ideally add.

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?

Three short sentences, front-loaded with the scope, then the exclusion, then the input prerequisite. Every clause carries load; nothing is repeated from the schema or the title.

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?

For a one-parameter read-only list tool with no output schema, the description covers scope, exclusions, alternatives and input sourcing adequately. The only gap is what the listing actually yields (e.g. paths relative to the repo root) and whether depth or limits apply.

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

Parameters4/5

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

Schema coverage is 100% and the single `repo` parameter already documents its regex pattern, so the baseline is 3. The description adds real meaning beyond the schema: that the name must be an Exeris *sibling* repo and that valid names come from `docs-list_repos`, which the schema does not say.

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?

States a specific verb (List) and resource (markdown documents under `<repo>/docs/**`) with an explicit glob scope and an explicit exclusion (`adr/`). It also names the sibling tools that own the excluded territory, so the agent can distinguish it from docs-list_adrs and docs-list_repo_docs-style siblings without opening a schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use vs when-not: adr/ files are out of scope and belong to `docs-list_adrs` / `docs-get_adr`. It also states the prerequisite for the single input by pointing at `docs-list_repos` for discovering valid repo names, which is exactly the decision an agent needs to make before calling.

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