Verified Handles

Set or suppress a deleted entry’s public notice

set_delete_notice

DestructiveIdempotent

Change what a deleted entry’s address shows: a public removal notice (HTTP 410 “This entry was removed”, with the date and the notice’s fixed line — wikidata_deleted, not_eligible, duplicate or terms — and the entry’s name unless hide_title), or none (notice: null), when it 404s as if it never existed. The delete’s own reason is never shown. Only a deleted entry (not a merged one). Audited; the cached page is purged. Dry run by default.

Input Schema

Name	Required	Description
`entry`	Yes	The entry: its VHID (11 digits), its short name (as in verifiedhandles.org/<short>), or its Wikidata QID (Q42).
`notice`	Yes	The notice, or null for none (the 404).
`dry_run`	No	true (the default): write nothing — show the change and the exact request it would send. false: make the change.
`hide_title`	No	Leave the entry’s name off the notice.

Output Schema

Name	Required	Description
`note`	No	A dry run: what to do next to make the change, in words.
`result`	No	A real run: the route’s own answer, where the tool adds facts of its own beside it.
`confirm`	No	A dry run of a change that needs it: the exact target to send back as `confirm` with dry_run: false.
`dry_run`	No	true: a dry run, which wrote nothing. Absent from a real run.
`replayed`	No	A real run with an idempotency_key already used for this change: the first call’s answer, given back; nothing was written now.
`would_send`	No	A dry run: the exact request the real run would send (`method`, `path`, any `headers` such as an Idempotency-Key, and its `body`, `form` or `query`), or the requests, in order.
`may_edit_live`	No	A dry run of a live edit: whether this key’s account may edit this entry live.
`refused_because`	No	A dry run the real run would be refused for: why, in words.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 27, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Goes well beyond annotations by explaining the HTTP 410 notice behavior, the fixed notice lines, hide_title effect, what happens when notice is null, and that the delete reason is never shown. It also states the operation is audited and purges the cached page, adding important mutation context.

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?

The key behavior is front-loaded: “Change what a deleted entry’s address shows.” Despite being dense, every clause carries useful information about notice content, null behavior, scope, audit/purge side effects, and dry-run default.

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?

Complete for a destructive mutation tool: annotations cover safety/idempotency, the schema fully documents parameters, and an output schema exists. The description supplies the remaining behavioral context an agent needs before invoking it.

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 the baseline is 3, but the description adds meaning beyond the schema by explaining what the notice enum values and null actually display, and how hide_title affects the public notice. It does not add much detail for the entry identifier beyond what the schema already documents.

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: changing what a deleted entry’s address shows, either a public removal notice or a 404. It also scopes the operation to deleted entries only, explicitly excluding merged entries, which distinguishes it from restore/keep/delete siblings.

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?

Gives clear conditions: only a deleted entry, not a merged one, and notes that dry run is the default. It does not explicitly name alternative sibling tools such as keep_wikidata_deleted_entry or restore_deleted_entry, so routing guidance is strong but not fully explicit.

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

All Verified Handles 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.