Quorus

Official

by Quorus-dev

Overview Schema Source Related Servers Discussions Admin

Python

Local

memory_delete

Remove a specific agent memory entry by room ID and key to comply with GDPR data deletion requests.

Instructions

Delete this agent's memory entry under key (GDPR).

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": {
      "room_id": "<room_id>",
      "key": "<key>"
    },
    "name": "memory_delete"
  }
}

Input Schema

Name	Required	Description	Default
`key`	Yes
`room_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.2Oct 18, 2026

TDQS

B3/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does add one real constraint not present in the schema: only 'this agent's' own memory can be deleted. However it says nothing about permanence/irreversibility, behavior when the key is absent, or idempotency.

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?

A single tight sentence with the destructive action and scope front-loaded; nothing is wasted. The stray double-backtick formatting around ``key`` is a minor blemish but not a comprehension problem.

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?

An output schema exists so return values need not be described, which lowers the bar. Still, for a destructive operation with two required parameters, the missing room_id semantics and the absence of any irreversibility or failure-mode note leave real gaps.

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

Parameters2/5

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

Schema description coverage is 0% for 2 parameters, so the description must compensate and only partially does: 'key' is named, but 'room_id' (a required parameter) is never mentioned and has no explanation anywhere. The room-scoping semantics of a delete are left entirely to inference.

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?

States a specific verb (Delete) plus resource (memory entry), and scopes it to 'this agent's' memory under a named key. The verb alone distinguishes it from the memory_set/memory_get/memory_list siblings, though the description never names them.

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

Usage Guidelines2/5

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

No when-to-use guidance and no comparison to siblings such as memory_set (which could overwrite instead of delete) or memory_list (to check what exists first). The parenthetical '(GDPR)' hints at a compliance motivation but does not tell an agent when this tool is the right choice.

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