Skip to main content
Glama

mistake_note_delete

Destructive

Delete a mistake note by its content hash. Restricts deletion to memories with memory_type='mistake', so only mistake entries are removed.

Instructions

Delete a mistake note by content hash. Only deletes memories with memory_type='mistake'.

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_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
content_hashYesContent hash of the mistake note to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.6/5.0
Behavior3/5

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

destructiveHint=true already tells the agent this is a destructive operation, so the annotation carries the safety signal. The description adds real value by bounding the blast radius to memory_type='mistake', but it does not state irreversibility, what happens if the hash matches a non-mistake memory, or what the result looks like.

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 short sentences, zero filler, with the action and its scope constraint front-loaded before any caveat. Every clause earns its place.

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 one-parameter destructive tool with full schema coverage and a destructiveHint annotation, the description covers action, key, and scope — enough to call it correctly. Only minor gaps remain around hash provenance and irreversibility/return behavior.

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% and the single parameter is documented as "Content hash of the mistake note to delete". The description's "by content hash" restates the schema rather than adding format, provenance, or validation detail, so 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?

The description opens with a specific verb+resource ("Delete a mistake note") and adds a scope qualifier ("Only deletes memories with memory_type='mistake'") that effectively separates it from the broader memory_delete sibling, even though that sibling is not named. The keying mechanism (content hash) is stated up front.

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?

The scope restriction implies when this tool is appropriate versus a general memory delete, but the guidance is only implied — there is no explicit "use X instead for other memory types" statement, and no prerequisite noted about where a valid content_hash comes from (e.g. mistake_note_search).

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