Skip to main content
Glama
Sign In
Body-MCP

Body-MCP

by sspublisher2005-gif
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

memory_delete

Deletes a specific stored memory by ID or clears all memories in a scope to remove data during cleanup.

Instructions

Delete one memory by id, or every memory in a scope (destructive).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "memory_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
scopeNo
memory_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, and it delivers only the single word '(destructive)'. It does not state whether deletion is permanent or reversible, whether confirmation is required, or what happens when memory_id and scope are both empty or both supplied — a dangerous ambiguity given both parameters default to an empty string.

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?

A single front-loaded sentence with no filler; the destructive nature is flagged inline rather than buried. Nothing in it is redundant or wasteful.

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

Completeness2/5

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

For an unannotated destructive mutation with two undocumented, defaulted parameters and no output schema, the definition is under-specified. The agent cannot tell what an empty scope deletes, whether the operation is irreversible, or what a success or failure response looks like.

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 0%, so the description must compensate, and it does partially by mapping memory_id to single-record deletion and scope to group deletion. It adds no detail on the empty-string defaults, on precedence when both are provided, or on how a scope string is matched.

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 names a specific verb (delete) and resource (memory) and distinguishes two operating modes: single-id deletion and scope-wide deletion. It is immediately clear what the tool does, though it does not reference any sibling tool by name to contrast against.

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 implied by the two modes: pass an id for one record, a scope for a group. There is no explicit statement of when to prefer this over other memory tools, no prerequisite or confirmation guidance, and no warning about calling it with neither parameter set.

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

Deploy Server

Other Tools