Skip to main content
Glama

record_decision

Records or updates an Architectural Decision Record so technical rules and conventions persist across agents, preventing decision drift.

Instructions

Records or updates an Architectural Decision Record (ADR) in Tier 2.

Call this tool whenever you establish a technical rule, make an architectural choice, or change an existing convention. Prevents decision drift and ensures subsequent agents (Claude, Codex, Antigravity) follow the agreed specification.

Lifecycle:

  • 'accepted': Active binding decision (automatically visible on Tier 1 State Card).

  • 'proposed': Under review or draft; not yet binding.

  • 'superseded': Replaced by a newer ADR; archived in Tier 2 history.

  • 'rejected': Proposed but explicitly abandoned with reason in rationale.

Formatting Rule: Preserve exact technical tokens in 'rationale' (e.g. file paths, PRAGMA flags, error codes, function signatures). Avoid fuzzy narrative paraphrasing.

Args: decision_id: Unique identifier string (e.g., 'ADR-001', 'ADR-STORAGE-WAL'). title: Short, descriptive title of the decision. rationale: Verbatim technical justification, constraints, and parameters. decided_by: Name or identity of the decider (e.g., 'claude', 'codex', 'human'). status: Decision status ('accepted', 'proposed', 'superseded', 'rejected').

Returns: str: Confirmation message with the recorded decision ID and status.

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": {
      "decision_id": "<decision_id>",
      "title": "<title>",
      "rationale": "<rationale>"
    },
    "name": "record_decision"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes
statusNoaccepted
rationaleYes
decided_byNoagent
decision_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does substantial work: it explains the four-state lifecycle, what superseded/rejected mean for history and visibility, and that accepted decisions surface automatically on the Tier 1 State Card. It stops short of stating permissions, whether an existing decision_id is overwritten or versioned, or how conflicts are handled.

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?

The description is sectioned (purpose, lifecycle, formatting rule, args, returns) and front-loaded, so an agent can scan it quickly. The 'Prevents decision drift and ensures subsequent agents...' sentence is motivational rather than operational, and the Returns block partly duplicates the output schema, but nothing is seriously bloated.

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 five-parameter mutation tool with no annotations, the definition covers purpose, state semantics, required argument formats, and a formatting constraint. Remaining gaps are upsert/overwrite behavior and authorization requirements; return values are already covered by the output schema.

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

Parameters5/5

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

Schema description coverage is 0% and status has no enum, yet the Args section documents all five parameters with concrete examples ('ADR-001', 'claude', 'codex', 'human') and enumerates the four valid status values with their semantics. This adds real meaning beyond the bare schema titles.

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 opens with a specific verb and resource: 'Records or updates an Architectural Decision Record (ADR) in Tier 2.' The upsert nature and the storage tier are stated up front, and the resource is clearly distinct from the sibling read/publish/update-task tools.

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 gives an explicit trigger condition: 'Call this tool whenever you establish a technical rule, make an architectural choice, or change an existing convention.' That is clear when-to-use guidance, but there is no when-not-to-use guidance and no named alternative (e.g. publish_context) for cases that are not ADR-worthy.

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