Skip to main content
Glama

docs-get_template

Fetch a canonical decision-doc template (ADR, RFC, or RESEARCH) to start structured Exeris documentation with the correct format and sections.

Instructions

Fetch one of the canonical decision-doc templates from exeris-docs/templates/. Three kinds: ADR (decision made), RFC (multi-option strategic question), RESEARCH (falsifiable hypothesis, lab-notebook shape).

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": {
      "kind": "<kind>"
    },
    "name": "docs-get_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesTemplate kind: ADR, RFC, or RESEARCH.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden; 'Fetch' and the repo path imply a read-only retrieval from a fixed template location, and the per-kind glosses hint at content shape. It does not state the return format (e.g., raw markdown), whether templates are static, or what happens if the path is missing, leaving real gaps.

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 tight sentences with the resource and its location front-loaded, followed by the taxonomy. Every clause carries information; nothing is padding.

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 tool with full schema coverage and no output schema, the description covers source location, the value space, and the meaning of each kind. A brief note on the returned content's form would close the only meaningful gap.

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 baseline would be 3, but the description genuinely adds meaning to each enum value: ADR = decision made, RFC = multi-option strategic question, RESEARCH = falsifiable hypothesis in lab-notebook shape. That is semantic guidance an agent can use to pick 'kind' correctly, beyond the schema's bare 'ADR, RFC, or RESEARCH'.

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?

Specific verb and resource: 'Fetch one of the canonical decision-doc templates from exeris-docs/templates/' pinpoints both the action and the exact artifact, distinguishing templates from concrete docs like docs-get_adr. It does not explicitly name a sibling to contrast with, so it stops 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 Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no mention of prerequisites or alternatives (e.g., docs-get_adr for an existing ADR versus this for a blank template). The only guidance is implicit in the kind taxonomy.

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