Skip to main content
Glama
Sign In
mcp-adr-analysis-server

mcp-adr-analysis-server

by tosin2013
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

generate_adr_from_decision

Generate a complete Architectural Decision Record from decision data, context, and consequences. Align with existing ADRs and choose a template format for consistent documentation.

Instructions

Generate a complete ADR from decision data. TIP: Reference @.mcp-server-context.md to align with existing architectural patterns and decisions.

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": {
      "decisionData": "<decisionData>"
    },
    "name": "generate_adr_from_decision"
  }
}

Input Schema

NameRequiredDescriptionDefault
adrDirectoryNoDirectory where ADRs are storeddocs/adrs
decisionDataYes
existingAdrsNoList of existing ADRs for numbering and references
templateFormatNoADR template format to usenygard

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

Annotations indicate readOnly=false and destructive=false, but description does not clarify side effects (e.g., whether it writes files, modifies state). No mention of output format or return value.

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?

The description is brief and to the point, with no irrelevant details. The tip is helpful.

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?

The description does not explain what happens after generation (e.g., file writing, output format, return value). Since there is no output schema, this is a significant gap for an agent to understand the tool's effect.

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

Parameters3/5

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

Schema includes descriptions for all parameters (adrDirectory, decisionData, existingAdrs, templateFormat), but the tool description does not add extra context. The 'decisionData' nested object is somewhat self-explanatory but not enhanced.

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 action (generate ADR) and input (decision data). However, it does not contrast with sibling tools like generate_adrs_from_prd or generate_adr_bootstrap, so less explicit about when to choose this one.

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?

Provides a tip to reference context file, but does not give explicit guidance on when to use this tool vs alternatives. Lacks conditional usage instructions.

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