Skip to main content
Glama

add_decision

Permanently record an architectural or product decision with a one-line summary. Appends the decision to the project record and updates summary.md for future reference.

Instructions

Record an architectural or product decision permanently.

Call when you make a choice that future sessions or contributors
should know about. Decisions show up in `summary.md` and in
`pjm wrap` context blocks.

Side effects: appends a `decision` event and updates summary.md.
Decisions are append-only — to revise, log a new decision that
supersedes the prior one (rather than editing).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
summaryYesOne-line description of the architectural or product decision (e.g., 'use bcrypt rounds=12 for password hashing'). Becomes part of the project's permanent record — write it for a future contributor.
locationNoOptional file path or scope where the decision applies (e.g., 'src/auth/' for a module-level choice). Helps precheck_file cite the decision when the file is later touched.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses side effects: appends a decision event and updates summary.md. Also states decisions are append-only and the supersede mechanism. Lacks details on authentication or failure modes, but acceptable for this simple tool.

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?

Very concise: three short paragraphs. First sentence captures purpose, second gives usage guidance, third covers side effects and revision. Front-loaded with key info, no wasted words.

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?

Tool has an output schema (not shown but indicated) so return values don't need explanation. Description covers purpose, usage, side effects, and revision strategy. Lacks prerequisites or error handling, but for a simple append-only tool it is sufficiently complete.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description adds value by explaining summary should be a one-line description for future contributors, and that location helps precheck_file cite the decision. This goes beyond schema descriptions.

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 clearly states the tool records architectural or product decisions permanently, specifying the verb 'record' and resource 'decision'. It distinguishes from siblings like add_note and log_issue by focusing on permanent decisions that future sessions need.

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?

Explicitly says 'Call when you make a choice that future sessions or contributors should know about.' It also explains decisions appear in summary.md and pjm wrap, and provides a revision strategy (log a new decision rather than editing). No explicit when-not-to-use, but context makes it clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/riponcm/projectmem'

If you have feedback or need assistance with the MCP directory API, please join our Discord server