Skip to main content
Glama

mistake_note_search

Read-only

Search mistake notes by semantic similarity to find known pitfalls and past errors before starting a task. Use an error message, context, or task description as the query.

Instructions

Search mistake notes by semantic similarity. Use before starting a task to check for known pitfalls and past errors.

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": {
      "query": "<query>"
    },
    "name": "mistake_note_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default: 5)
queryYesSearch query (error message, context, or task description)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.8/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes this as a safe, non-mutating operation, so the description's burden is reduced. It adds useful behavioral context by revealing that matching is semantic rather than keyword-based, which affects how the agent should phrase queries, but says nothing about ranking, result shape, or behavior when no matches exist.

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?

Two sentences, zero waste, with the purpose front-loaded ahead of the usage instruction. Nothing redundant or padded.

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 simple two-parameter read tool with full schema coverage and a safety annotation, the description covers purpose, trigger, and matching method. The one remaining gap is the shape of returned results, but the tool is simple enough that this is a minor omission rather than a blocker.

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 both parameters are already documented, including examples of valid query content and the default for limit. The description adds only the semantic-matching framing, which indirectly suggests natural-language queries but adds no new syntax or constraint beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 (search) and a specific resource (mistake notes), plus the matching mechanism (semantic similarity), which distinguishes it from the mutation siblings mistake_note_add/delete/update. It does not explicitly distinguish itself from the broader memory_search sibling, but the resource scope is clear enough to select on.

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

Usage Guidelines4/5

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

Gives an explicit usage trigger: 'Use before starting a task to check for known pitfalls and past errors.' That is a concrete when-to-use condition rather than an implied one. It provides no when-not guidance or named alternative, so it stops short of a 5.

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