Skip to main content
Glama

mistake_note_update

Update fields in an existing mistake note, such as failure count, error pattern, context signature, and corrective actions; content changes generate a new hash and re-store the note.

Instructions

Update fields of an existing mistake note. Can update failure_count, error_pattern, context_signature, incorrect_action, or correct_action. Content changes create a new hash (delete + re-store).

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": {
      "content_hash": "<content_hash>"
    },
    "name": "mistake_note_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
content_hashYesContent hash of the mistake note to update
error_patternNoUpdated error pattern
failure_countNoNew failure count
correct_actionNoUpdated correct action
incorrect_actionNoUpdated incorrect action
context_signatureNoUpdated context

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?

Exceeds what destructiveHint=false alone conveys by disclosing that content changes rotate the hash via delete + re-store — important, since the caller's content_hash reference becomes stale. The delete + re-store framing sits in mild tension with destructiveHint=false, but the description explicitly says content is re-stored, so the operation preserves data rather than destroying it.

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?

Three short sentences, front-loaded with the action, then the field list, then the hash-rotation caveat. Every sentence carries information an agent needs and nothing is padded.

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

Completeness3/5

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

For a flat six-parameter mutation with no output schema and sparse annotations, the description covers the fields and the hash side effect but omits merge semantics, error behavior for a missing/invalid content_hash, and what the tool returns. Adequate to call correctly, not adequate to predict the outcome confidently.

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 six parameters with the same field names used in the description. The description adds no semantics beyond the schema — nothing on whether omitted fields are preserved (merge vs. replace), value formats, or failure_count unit/reset behavior.

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?

Clear specific verb + resource ("Update fields of an existing mistake note") followed by an enumeration of the updatable fields. The sibling name mistake_note_add implies creation vs. updating, but the description never states the distinction itself, so differentiation rests on the name rather than the text.

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 only implied: "existing" and the required content_hash signal that this is for notes already stored, versus mistake_note_add for new ones. No explicit when-to-use, when-not-to-use, or prerequisite (e.g., obtaining a content_hash, behavior when the hash is unknown) is given.

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