Skip to main content
Glama

record_decision

Record a coding decision before implementing changes so reviewers can approve or reject it, keeping architecture, API, and security choices visible and auditable.

Instructions

Record a decision before making the changes that carry it out, so reviewers can approve or reject it. Use one call per decision (architecture, data model, API, business rule, dependency, security, performance, testing, quality).

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": {
      "title": "<title>",
      "kind": "<kind>",
      "why": "<why>",
      "files": "<files>"
    },
    "name": "record_decision"
  }
}

Input Schema

NameRequiredDescriptionDefault
whyYesthe reason in one or two plain sentences
kindYesarchitecture, data-model, api, business-rule, dependency, security, performance, testing, quality or other
riskNowhat could go wrong, if anything
filesYesfiles this decision changes
titleYesshort headline, at most 8 words, e.g. Rate limit per client IP
alternativesNooptions considered and not chosen

Output Schema

NameRequiredDescriptionDefault
idYes
statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 behavioral burden, and it does usefully disclose the review-gating workflow (a recorded decision feeds an approve/reject step). It does not explain consequences of the review outcome, whether recording blocks later changes, or whether repeated calls create duplicates, leaving real behavioral gaps for a mutation tool.

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?

Two sentences, front-loaded with purpose and timing, with no filler. The parenthetical category list partially duplicates the schema's kind description, which is the only waste.

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

Completeness3/5

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

For a 6-parameter mutation tool with an output schema, the description conveys why and when but omits the lifecycle around the decision (rejection handling, idempotency, whether the change is blocked until approval). The core call path is covered; the surrounding behavior is not.

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 six parameters including the kind taxonomy and file list. The description only restates the decision categories and adds the 'one call per decision' cardinality note, which is marginally useful but largely duplicative.

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?

The description gives a specific verb and resource ('Record a decision') plus a clear intent ('so reviewers can approve or reject it'), which makes the tool's role easy to grasp. It does not explicitly contrast with siblings like get_review_feedback or show_behavior, so differentiation is inferred rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

It states the timing condition clearly: record the decision 'before making the changes that carry it out', and adds the granularity rule 'Use one call per decision'. It stops short of naming when not to use it or pointing to a specific alternative tool for other workflows.

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