past.dev

Show where a memory deletion stands

get_memory_deletion

Read-onlyIdempotent

Shows where a deletion that delete_memory or the Memory API accepted stands: its source ids and its status, deleting while their stored copies and index entries are being purged, then deleted once none is left. Recall stops returning them as soon as the deletion is accepted. Needs project Read.

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": {
      "operationId": "<operationId>"
    },
    "name": "get_memory_deletion"
  }
}

Input Schema

Name	Required	Description	Default
`project`	No	The project's slug, exactly as list_projects returned it. Omit it only when the organization has one live project.
`operationId`	Yes	The deletion's operationId, as delete_memory or the API answered it.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Beyond the readOnlyHint and idempotentHint annotations, it discloses the permission requirement ('Needs project Read') and describes the state machine: 'deleting' while copies and index entries are purged, then 'deleted'. That is real added context; only the absence of any latency/retention expectations keeps it from a 5.

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?

Front-loaded with what it shows, then the state semantics, then the permission requirement last. Dense and mostly waste-free, though the core sentence is a long run-on that could be split for easier scanning.

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?

For a two-parameter read-only status tool with no output schema, the description supplies the return contents (source ids, status), the meaning of each status value, and the permission prerequisite. Nothing an agent needs to call it or interpret the result 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 description coverage is 100%, and both parameters (project slug with its single-project fallback, operationId as UUID) are fully documented in the schema. The description repeats the operationId concept but adds no syntax or format guidance beyond the schema, so the baseline 3 applies.

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 ('Shows where a deletion ... stands') and enumerates what is returned: source ids and status. It also names the origin of the operation ('a deletion that delete_memory or the Memory API accepted'), which cleanly separates it from the destructive sibling delete_memory.

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

Usage Guidelines4/5

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

Implies the workflow: this tool is used after delete_memory or the API has accepted a deletion, to observe its progress. It also clarifies that recall stops returning the records immediately, removing the temptation to re-poll recall. It stops short of explicitly saying to poll until status reaches 'deleted'.

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

All past.dev tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?