Skip to main content
Glama
Sign In
mcp-adr

mcp-adr

by mauriziomocci
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

adr_overview

Generate an overview diagram of all Architecture Decision Records (ADRs), optionally filtered by status to focus on specific decisions.

Instructions

Generate an overview diagram of all ADRs (optionally filtered by status).

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": "adr_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNomermaid
status_filterNo
project_pathNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, description provides minimal behavioral context. States 'generate' but does not explain side effects, output format, or that it likely returns a diagram (implied by format parameter). No mention of data persistence or modifications.

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

Conciseness4/5

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

Single sentence with no fluff. Could be slightly expanded for clarity without becoming verbose.

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

Completeness2/5

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

Given 14 sibling tools and 3 parameters, the description is too sparse. Does not explain output schema (though exists), usage context, or how it differs from similar diagram tools. Inadequate for accurate selection.

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

Parameters2/5

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

Schema description coverage is 0%, so description must explain parameters. It only references the status_filter via 'filtered by status', but does not explain 'format' (default mermaid) or 'project_path' (likely needed for project context). Partial compensation.

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?

Clearly states it generates an overview diagram of ADRs with optional status filter. However, sibling 'adr_diagram' also produces diagrams, and the description does not differentiate them.

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?

No guidance on when to use this tool versus alternatives like adr_diagram or adr_list. Does not specify exclusions or prerequisites.

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