Skip to main content
Glama

docs-list_repos

Lists sibling Exeris repositories under the ecosystem root that contain a docs/ directory, returning repo names for use with repository documentation lookup tools.

Instructions

List sibling Exeris repos under the ecosystem root that publish a docs/ directory. Returned names are usable as repo input to docs-list_repo_docs and docs-get_repo_doc.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "docs-list_repos"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose real behavior beyond the name: scope is limited to the ecosystem root and results are filtered to repos containing a `docs/` directory, and the return payload is names. It does not state ordering, what happens when no repos match, or that the call is side-effect free, which is a moderate gap for an unannotated tool.

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?

Two sentences, both load-bearing: the first defines scope and filter, the second defines how the output is consumed. The most important constraint (which repos qualify) is front-loaded, and there is no redundant restatement of the tool name.

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 zero-parameter, no-annotation, no-output-schema list tool, the description covers what it returns and how to use the result, which is what an agent needs to call it correctly. Minor omissions remain: ordering, empty-result behavior, and whether discovery is recursive or limited to direct siblings.

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?

The tool takes zero parameters, so there is nothing to disambiguate and the baseline of 4 applies. The description appropriately spends its words on scope and return-value meaning instead of inventing parameter detail.

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?

Uses a specific verb+resource ('List ... repos') and adds a discriminating filter: only sibling repos under the ecosystem root that publish a `docs/` directory. It also names the two siblings that consume its output, so an agent can tell it apart from docs-list_repo_docs and docs-get_repo_doc without opening either schema.

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

Usage Guidelines4/5

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

The second sentence gives clear implied routing: call this first to obtain a valid `repo` value for docs-list_repo_docs and docs-get_repo_doc. It stops short of explicit when-not-to-use guidance or stating that this is the required entry point for repo discovery, so it is clear context rather than full exclusion rules.

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