Skip to main content
Glama
Sign In

Wicked MCP

by io.github.WickedAPI
OverviewDiscussionsAdmin

memory_delete

Destructive

[Wicked Memory] PERMANENTLY hard-delete a memory (right-to-be-forgotten). Default scope "chain" removes every version; "version" only this one. Only an audit row (no content) is kept.

Use when you must permanently erase a memory (right to be forgotten). Not for correcting it (use memory_update, which keeps history).

Behavior: DESTRUCTIVE and not reversible; confirm intent before calling.

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": {
      "wallet": "<wallet>",
      "memory_id": "<memory_id>",
      "timestamp": "<timestamp>",
      "nonce": "<nonce>",
      "signature": "<signature>"
    },
    "name": "memory_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
nonceYesFrom memory_prepare (single use).
scopeNo"chain" (all versions, default) or "version".
reasonNoOptional audit-log note (max 200 chars).
walletYesYour agent's 0x wallet address.
memory_idYesUUID of any version in the chain.
signatureYesYour wallet's signature over memory_prepare's message_to_sign.
timestampYesFrom memory_prepare.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and non-idempotent behavior, but the description adds material context: deletion is irreversible, an audit row without content is retained, default chain scope removes every version, and intent should be confirmed before calling. This is exactly the extra behavioral information an agent needs for a destructive operation.

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?

The description is front-loaded with the destructive action and scope behavior, then gives usage routing and a safety warning. There is some repetition around permanence and destructiveness, but for a high-risk deletion tool the redundancy is defensible rather than wasteful.

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

Completeness5/5

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

Given the rich annotations and fully described schema, the description supplies the missing behavioral context: irreversibility, audit retention, scope consequences, and a confirmation warning. No output schema exists, but the key outcome (audit row retained, content deleted) is stated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so parameter documentation is already strong and the baseline would be 3. The description adds consequence-level meaning for the scope parameter by explaining that default chain scope removes every version while version scope removes only one, which is useful beyond the schema's brief scope note.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: permanently hard-delete a memory. It also specifies scope behavior (chain vs version) and explicitly distinguishes this from memory_update, so the agent can identify it among memory siblings.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use condition (permanent erasure / right to be forgotten) and a clear when-not-to-use alternative (correcting a memory should use memory_update). The routing guidance is unambiguous.

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

All Wicked MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources