A2UI Atomic Catalog

delete_reading

DestructiveIdempotent

Permanently remove one or more of the reader's saved readings from their History. Takes an array so the Workspace's multi-select can delete a batch in one call rather than one round trip per row. Ids that don't exist (or belong to someone else's history) are silently skipped — the response's deleted count says how many rows actually went, never assume it equals the number of ids you sent.

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": {
      "ids": "<ids>"
    },
    "name": "delete_reading"
  }
}

Input Schema

Name	Required	Description	Default
`ids`	Yes	Reading ids from list_readings. A single-item array deletes one row.

Output Schema

Name	Required	Description
`note`	No	Guidance for the caller.
`reason`	No	Why nothing was deleted.
`deleted`	No	Rows deleted.
`available`	Yes	False when there is no signed-in reader or the store failed.
`requested`	No	Ids requested.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Goes well beyond the annotations: it discloses that non-existent or other-user ids are silently skipped rather than erroring, and that the `deleted` count may be lower than the ids sent. That is exactly the kind of failure-mode detail an agent cannot infer from destructiveHint/idempotentHint alone, and nothing here contradicts those hints.

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?

Three sentences, front-loaded with the destructive action, then batching rationale, then the skip/count caveat. No filler and each sentence carries information an agent needs before calling.

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 one-parameter destructive tool with full annotation coverage and an output schema, this is complete: it covers what is removed, how batches behave, and how to read the result. Nothing material is left for the agent to guess.

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 the schema already documents the ids array, its source (list_readings), and the single-item case — the description mostly restates that. The silent-skip note adds real meaning about how ids are interpreted, but the array semantics themselves are not new information.

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 remove ... saved readings from their History'), and the 'permanently' qualifier plus the History scope make it clearly distinct from siblings like list_readings and save_reading without needing to open the schema.

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?

Explains when the array form is appropriate ('Workspace's multi-select ... a batch in one call'), which gives real usage context. It stops short of naming any alternative tool or stating a when-not-to-use condition, so it is clear context without explicit routing.

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

All A2UI Atomic Catalog tools Inspect

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.