Skip to main content
Glama

Record a decision

record_decision

Capture a dated decision and its outcome to close a decision point and preserve a clear record of what was chosen and when.

Instructions

Close a dated decision point with what was decided.

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": {
      "date": "<date>",
      "outcome": "<outcome>"
    },
    "name": "record_decision"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes
outcomeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does not disclose whether this creates or overwrites a record for a given date, whether decisions can be amended or removed, what permissions are needed, or what the response contains.

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?

A single short sentence with no filler, and the essential constraint (dated) is front-loaded. It is efficient, though its terseness contributes to the gaps in other dimensions.

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?

For a mutation tool with no annotations, no output schema, and zero schema description coverage, the definition is far too thin. An agent knows only that a date and an outcome string are required, with no idea of write semantics, idempotency, or return value.

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 both parameters are undocumented beyond their names and the date pattern. The description mentions a 'dated' decision and 'what was decided', which loosely maps to date and outcome, but adds no meaning such as accepted date formats, whether outcome must be free text, or what values outcome typically holds.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific action and resource ('Close a dated decision point') with a stated input ('what was decided'), which is more specific than the bare name. However, the verb 'close' and 'decision point' are unusual vocabulary that isn't grounded anywhere, so an agent can't fully tell what object is being mutated or how it differs from siblings like save_reflection or quarterly_review.

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?

There is no explicit when-to-use guidance, no prerequisites, and no named alternatives. The word 'dated' hints that a date is required, but nothing tells the agent when recording a decision is appropriate versus using save_reflection or add_win.

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