mcp-server-decisions

Overview Schema Source Related Servers Discussions Admin

record-decision

Register a technical decision by documenting the problem, chosen solution, rejected alternatives, and technologies involved.

Instructions

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": {
      "problem": "<problem>",
      "chosen_solution": "<chosen_solution>",
      "rejected_alternatives": "<rejected_alternatives>",
      "technologies": "<technologies>"
    },
    "name": "record-decision"
  }
}

Input Schema

Name	Required	Description	Default
`domain`	No	Technical domain (e.g., 'data-engineering', 'backend', 'ai')
`status`	No	Decision status	ACTIVE
`adr_ref`	No	Reference to an associated ADR, if any (e.g., 'docs/adr/adr-012-duckdb.md')
`problem`	Yes	The problem or technical opportunity identified
`predictions`	No	Initial predictions known at decision time (optional)
`technologies`	Yes	Technologies involved in this decision (e.g., ['duckdb', 'parquet'])
`chosen_solution`	Yes	The solution that was chosen
`rejected_alternatives`	Yes	Alternatives considered and rejected

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.2Jul 28, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations exist, so the description must carry the full burden. It states 'Register' (implying creation) but does not disclose side effects (e.g., whether it overwrites, requires special permissions, or has constraints). A mutation tool with no annotation coverage should offer more behavioral context.

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 a single sentence with no wasted words, front-loaded with the verb 'Register', and covers the essential aspects efficiently.

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?

With 8 parameters, no output schema, and no annotations, the description is too brief. It doesn't explain return values, behavior on conflicts, prerequisites, or post-conditions. The tool's complexity merits a more comprehensive description.

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 description coverage is 100%, so the schema already documents all parameters. The description lists only four of eight parameters (problem, solution, alternatives, technologies) but adds no new meaning beyond what the schema provides. Baseline 3 is appropriate.

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?

The description uses a specific verb 'Register' and noun 'technical decision', and lists key components (problem, solution, alternatives, technologies), clearly distinguishing it from query-decisions (retrieval) and record-prediction/outcome (related but different actions).

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 description implies when to use (when registering a decision) but provides no explicit guidance on when not to use, nor mentions sibling tools like query-decisions as alternatives for retrieval. Usage context is implied but not clarified.

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

Deploy Server