Skip to main content
Glama

remember_decision

Read-onlyIdempotent

Capture decisions in real time during a session. High-confidence inputs enter the active knowledge graph immediately, mid-confidence queue for human approval, and low-confidence are dropped, with per-session dedup and rate-limit.

Instructions

Live agent write into the decision knowledge graph. Confidence-scores the input and routes it through the memoir review queue: high-confidence rows enter the active graph immediately, mid-confidence rows queue for human approval, low-confidence rows are dropped without persistence. Per-session dedup + rate-limit. Use during a session to capture decisions in real time. For manual high-confidence writes use add_decision; for post-hoc extraction from session logs use mine_sessions. Returns JSON: { id, review_status, confidence, deduplicated? }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesShort summary of the decision
contentYesFull decision text — reasoning, context, tradeoffs
typeYesDecision type
service_nameNoSubproject name this decision is about (e.g., "auth-api", "user-service")
symbol_idNoSymbol FQN this decision is about (e.g., "src/auth/provider.ts::AuthProvider#class")
file_pathYesFile path this decision is about
tagsNoTags for categorization (e.g., ["auth", "security"])
session_idNoSession identifier for dedup/rate-limit (default: "_default")
git_branchNoGit branch this decision belongs to. Omit to auto-detect, or pass null to make it branch-agnostic.
Behavior1/5

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

The description states it writes into the knowledge graph, but annotations set readOnlyHint=true, a direct contradiction. This misleads agents about side effects despite other annotations being consistent.

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?

Four sentences, front-loaded with the tool's core behavior. Every sentence adds value—no filler. Extremely concise while covering purpose, behavior, usage, and return format.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (9 params, confidence routing, dedup, rate-limit, no output schema), the description explains the entire flow, return format, and sibling tools, making it fully complete for agent usage.

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%, so baseline is 3. The description adds high-level context (dedup, rate-limit) but does not elaborate on individual parameters beyond the schema. Adequate for understanding parameter purpose.

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 it writes into the decision knowledge graph with confidence-based routing, and explicitly distinguishes from siblings 'add_decision' and 'mine_sessions', providing specific verb+resource and differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clearly advises 'Use during a session to capture decisions in real time' and specifies when to use alternatives: 'For manual high-confidence writes use add_decision; for post-hoc extraction from session logs use mine_sessions.'

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/nikolai-vysotskyi/trace-mcp'

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