Skip to main content
Glama

docs-list_adrs

Lists ADRs from the Exeris ecosystem registry with number, title, owning repo, scope, visibility, status, and link. Filter by status to find accepted, proposed, or superseded decisions.

Instructions

List all ADRs from the Exeris ecosystem registry. Each entry carries number, title, owning repo, scope, visibility, status, and link. Optional status filter narrows the result by the first token of the status cell (e.g. 'accepted', 'proposed', 'superseded', 'reserved').

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_adrs"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNoFilter to entries whose status.state equals this value (case-insensitive; trimmed before comparison).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

A3.7/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 the result shape (number, title, repo, scope, visibility, status, link), which is genuinely useful given there is no output schema, but says nothing about result volume, ordering, pagination, or whether the registry scan requires permissions.

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 compact sentences, front-loaded with the resource and scope, then the return fields, then the filter. Nothing is redundant and no sentence is filler.

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-required-parameter list tool with no output schema, the description covers purpose, result fields, and filter behavior adequately. The remaining gap is operational detail (ordering, completeness of the scan, truncation) that an agent might want before relying on the full listing.

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%, so the baseline would be 3, but the description adds real meaning: it explains the filter keys off the first token of the status cell and supplies concrete example values ('accepted', 'proposed', 'superseded', 'reserved') in place of the missing enum. That goes beyond the schema's case-insensitive equality note.

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

Purpose4/5

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

States a specific verb and resource ("List all ADRs from the Exeris ecosystem registry") and enumerates the returned fields, so the agent knows exactly what the tool yields. It does not explicitly contrast itself with the singular sibling docs-get_adr, which keeps it short of a 5.

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 optional status filter implies a browse-and-narrow use case, but the description never says when to choose this over docs-get_adr (single ADR) or docs-search. No exclusions or prerequisites are given, leaving routing to inference.

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