Skip to main content
Glama
nikolai-vysotskyi

trace-mcp

by nikolai-vysotskyi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

remember_decision

Capture decisions in real time during a session by confidence-scoring input and routing high-confidence rows to the active graph, mid-confidence to review, and dropping low-confidence.

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

A4.7/5.0
Behavior5/5

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

Annotations only cover the safety profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false). The description goes well beyond them: confidence-based routing with three explicit outcomes (immediate graph entry, human review queue, silent drop without persistence), plus per-session dedup and rate limiting. This is exactly the behavioral detail an agent needs before writing.

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?

Front-loaded with the core action, then routing behavior, then constraints, then alternatives, then return shape. Dense but every sentence carries distinct information with no repetition.

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?

For a 9-parameter mutation tool with no output schema, the description supplies the missing return shape ({ id, review_status, confidence, deduplicated? }), the persistence semantics, and the dedup/rate-limit constraints. An agent has everything needed to call it correctly and predict the outcome.

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 9 parameters including session_id's dedup/rate-limit role. The description restates session-level dedup but adds no new syntax or meaning for tags, file_path, symbol_id, git_branch, or service_name, so the baseline 3 applies.

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?

States a specific verb+resource ("write into the decision knowledge graph") and immediately scopes it as a live, in-session write. It explicitly distinguishes itself from the two nearest siblings, add_decision and mine_sessions, so an agent can route without opening schemas.

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?

Gives explicit when-to-use ("during a session to capture decisions in real time") plus named alternatives for the two adjacent cases: add_decision for manual high-confidence writes, mine_sessions for post-hoc log extraction. Nothing is left to inference.

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