Skip to main content
Glama

note_decision

Record each design decision as a dated line in PROJECT.md so later changes preserve approved choices and do not undo them.

Instructions

Note a design decision in PROJECT.md as one dated line, as ONE change: each choice a later context should not undo (a part and why, a board size, what the person approved).

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": {
      "text": "<text>"
    },
    "name": "note_decision"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
textYese.g. "TJA1051 over MCP2551: 3.3 V I/O"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description bears the full burden, and it does disclose useful traits: the write target (PROJECT.md), the appended format (one dated line), and atomicity ('as ONE change'). It does not state whether the file is created when absent, whether writes are idempotent, or what the tool returns — meaningful gaps for a mutation tool with zero annotation coverage.

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 front-loaded sentence with no filler, and the destination and format come early. It is slightly overpacked, with a clause and a three-item parenthetical stacked after the colon, and 'as ONE change' is terse enough to be ambiguous.

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 two-parameter append-style tool with no output schema and no annotations, the essentials (what to record, where, in what format) are covered. It falls short on the undocumented `file` parameter and on edge behavior such as file creation or repeated entries.

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 coverage is 50%: `text` has an example, `file` has nothing. The description adds real semantic value for the content parameter by enumerating what belongs in a decision line (a part and why, a board size, an approval), but it never mentions the `file` parameter, leaving the override of the PROJECT.md default undocumented in both schema and description.

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 pairs a specific verb ('Note') with a specific resource and destination ('a design decision in PROJECT.md'), and specifies the output shape ('one dated line'). That reliably separates it from the board-editing siblings such as add_trace or add_part, though it never explicitly names an alternative.

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?

Guidance is present but encoded in a phrase rather than stated as a condition: 'each choice a later context should not undo' tells the agent what qualifies as worth recording. There is no explicit when-not, no mention of how this differs from other recording tools, and no prerequisite/permission guidance.

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