Skip to main content
Glama
nikolai-vysotskyi

trace-mcp

by nikolai-vysotskyi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

remember_decision

Read-onlyIdempotent

Capture live decisions during a session, score confidence, and route high-confidence entries straight to the knowledge graph while queueing mid-confidence ones for human review.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.22.0
    • changedInput schema / required
      Previous value: -[
-  "title",
-  "content",
-  "type",
-  "file_path"
-]New value: +[
+  "title",
+  "content",
+  "type"
+]
  2. Changed1 schema field changedv3.3.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  3. Addedv1.41.0
  4. Removedv1.38.0
  5. Addedv1.36.1

TDQS

A3.7/5.0
Behavior1/5

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

The description contradicts the annotations: it says 'Live agent write into the decision knowledge graph' and discusses persistence, while annotations declare readOnlyHint=true. Per the scoring rule, this contradiction forces a score of 1. The otherwise rich behavioral detail (confidence routing, dedup, rate limit) cannot be trusted alongside contradictory metadata.

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?

The description is compact and front-loaded with the core action, and every sentence contributes useful information: routing behavior, usage context, alternatives, and return shape. The middle sentence is dense but still readable.

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?

For a 9-parameter tool with no output schema, the description covers the important non-schema context: confidence tiers, review queue behavior, dedup/rate-limit, and the JSON return shape. It could add permission requirements or rate-limit specifics, but the essentials are present.

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 description coverage is 100%, so the schema already documents all nine parameters. The description adds almost nothing parameter-specific beyond connecting session_id to dedup/rate-limit behavior, so the baseline of 3 is appropriate.

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 names a specific action ('write into the decision knowledge graph') and clearly differentiates from siblings by referencing add_decision and mine_sessions. The confidence-routing behavior further clarifies what this tool uniquely does.

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?

Explicitly states when to use it ('during a session to capture decisions in real time') and names two alternatives with their appropriate conditions: add_decision for manual high-confidence writes and mine_sessions for post-hoc extraction. This gives an agent clear routing guidance.

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

Deploy Server

Other Tools