Skip to main content
Glama
Sisuthros

claude-amplifier

amplify_decisions

Record, search, and update project design decisions with rationale, outcomes, and dependencies. Get reminders for overdue check-ins.

Instructions

Track and query architectural / design decisions for a project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
opYesOperation: track=add new, get=list active, search=text search, supersede/revert=replace decision, update=refine fields without superseding (v1.2.0), update_outcome=mark validation, overdue=list decisions whose check-in passed.
projectNoProject name. Required for track/get.
categoryNoDecision category (e.g. 'architecture', 'tooling', 'security'). Defaults to 'general'.
titleNoShort decision title. Required for track.
descriptionNoFull description. Required for track.
rationaleNoWhy this decision was made (optional).
tagsNoTags (optional).
queryNoText to search for. Required for op=search.
idNoDecision id. Required for supersede/revert/update/update_outcome.
outcome_check_inNoWhen to follow up on this decision. Relative ('+7d', '+30d') or ISO date. Surfaces in 'overdue' when past due.
outcome_statusNoFor op=update_outcome: mark whether the decision worked. Defaults to 'validated'.
restore_stepNoHow to restore this decision if the system gets reset (e.g. container recreate, image pull). Surfaces in active reminders every session.
next_stepNoConcrete next action when this decision is unblocked.
blocked_onNoWhat this decision is waiting on (person, event, dependency).
trade_offsNoTradeoffs accepted when choosing this decision.
alternatives_consideredNoAlternatives considered and rejected.
supersedesNoID of an older decision this one replaces. The old one is automatically marked 'superseded'.
relationsNoKnowledge-graph links to other decision IDs by relation type.
Behavior3/5

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

No annotations exist, so the description carries full behavioral disclosure burden. It outlines core operations (track, get, search, supersede, etc.) but doesn't detail side effects, auth requirements, or data persistence. The schema provides parameter details but not behavioral traits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence that front-loads the purpose. However, given the tool's complexity (18 parameters, multiple operations), the description is too brief and could benefit from a more structured format (e.g., bullet points) to improve scanability.

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 complex tool with many operations and nested objects, the description is minimal. No output schema exists, and the description doesn't explain return values or result formats. The effort required from the agent to understand behavior is higher than necessary.

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 100% with detailed parameter descriptions. The one-line description adds no additional parameter-level semantics beyond the schema. Baseline 3 is appropriate as the schema already explains inputs well.

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 clearly states the tool tracks and queries architectural/design decisions, using a specific verb and resource. It distinguishes the tool's domain (decisions) from siblings like amplify_evidence_chain or amplify_record_claim, though it doesn't explicitly differentiate operations.

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?

No guidance on when to use this tool versus alternatives. The description only states the broad function without mentioning prerequisites, context, or exclusions. The schema lists operations but doesn't provide usage context.

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/Sisuthros/claude-amplifier'

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