Skip to main content
Glama

rr_delete_memory_entry

DestructiveIdempotent

Delete a saved memory entry by specifying its namespace and key, removing outdated or incorrect data from a granted context namespace.

Instructions

Delete one saved memory entry by namespace and key. The namespace must have been granted to this API key.

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": {
      "namespace": "<namespace>",
      "key": "<key>"
    },
    "name": "rr_delete_memory_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesThe entry's key within the namespace, up to 200 characters.
namespaceYesA context namespace this key has been granted, for example supplier_rules.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructive=true, idempotent=true, readOnly=false and closed-world, so the safety profile is carried by structured data. The description adds real value beyond that by disclosing the authorization constraint tying the namespace to the API key's grants. It does not say whether the delete is hard or recoverable, or what error surfaces if the grant is missing.

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, both front-loaded and free of filler: the action and its scope come first, the constraint second. Nothing is redundant with the schema and nothing could be cut.

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 two-parameter destructive tool with full annotation coverage and no output schema, the description covers purpose, identity semantics, and the authorization gate. Minor gaps remain around failure behavior when the namespace is not granted, but no essential calling information is missing.

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 both parameters are already documented with examples and length limits, so the schema does the heavy lifting. The description only restates that the two parameters identify a single entry and reinforces the grant requirement for namespace, which adds little beyond the schema.

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 gives a specific verb and resource ('Delete one saved memory entry') plus the identifying dimensions ('by namespace and key'), which cleanly separates it from the read/save/list siblings. It stops short of explicitly contrasting with those siblings, but the scope is unambiguous.

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?

A prerequisite is stated ('namespace must have been granted to this API key'), which is the main gate on use. There is no explicit when-to-use versus when-to-use-an-alternative guidance, though for a single-entry delete the alternative (no deletion) is implicit.

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