Skip to main content
Glama

mistake_note_add

Record a mistake pattern with its context, incorrect action, and correct action to enable error replay and track repeated failures.

Instructions

Record a mistake pattern for error replay. Tracks what went wrong and the correct action. Auto-increments failure_count for repeated patterns.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "error_pattern": "<error_pattern>",
      "context_signature": "<context_signature>",
      "incorrect_action": "<incorrect_action>",
      "correct_action": "<correct_action>"
    },
    "name": "mistake_note_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
error_patternYesThe error pattern or message
correct_actionYesWhat should have been done instead
incorrect_actionYesWhat was done incorrectly
context_signatureYesContext where the error occurred (file, function, task type)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only supply destructiveHint=false, so the description must carry behavioral weight. It does add one genuinely non-obvious trait: failure_count auto-increments for repeated patterns, signaling match-on-signature behavior rather than blind insertion. It stops short of saying whether an existing note is updated vs. duplicated, or what identifier is returned.

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?

Three short sentences with the purpose front-loaded and the side-effect detail placed last where it belongs. Minor redundancy between the first two sentences ('mistake pattern' / 'what went wrong') and the unexplained 'error replay' phrase keep it from a 5.

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 four-required-parameter write tool with no output schema, the description covers purpose, recorded content, and a key side effect. Missing only the return value (e.g., an id) and deduplication behavior, which are secondary given the fully documented schema.

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 all four parameters (error_pattern, context_signature, incorrect_action, correct_action) are already documented. The description restates the intent of incorrect_action and correct_action but adds no format, length, or canonicalization guidance for context_signature, so the baseline 3 applies.

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?

States a specific verb+resource ('Record a mistake pattern') and clarifies the payload semantics with 'Tracks what went wrong and the correct action'. The 'add' versus sibling update/search/delete distinction is left to the name rather than stated in the description, so sibling differentiation is implicit.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: one infers this is called when a mistake is identified. There is no explicit guidance on when to use this versus mistake_note_update, nor any prerequisites. The failure_count note mildly implies that repeats should still go through add, but this is left for the agent to infer.

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