Verified Handles

Restore a deleted entry

restore_deleted_entry

Destructive

Bring a deleted entry back onto the public site, as it was; any public removal notice goes. Name it by its VHID (a deleted entry has no public short name). A merged entry stays deleted while it redirects: undo the merge with unmerge_entry instead. Audited. Dry run by default.

Input Schema

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

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 10, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the annotations, the description discloses that any public removal notice goes away, that merged entries remain deleted unless unmerged, that the action is audited, and that dry run is the default. This is substantial behavioral context for a mutation tool with destructiveHint=true.

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 description is compact and front-loaded with the main action. Every sentence adds relevant information: scope, identifier handling, the merge exception, auditing, 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?

Given the annotations, full schema coverage, and presence of an output schema, the description covers what an agent needs: the restore effect, the merge exception, the identifier nuance, audit behavior, and dry-run default.

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 schema already documents both parameters. The description still adds useful meaning by explaining why the entry should be specified as a VHID for deleted entries, though it does not go beyond the schema on dry_run behavior.

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?

The description states a specific verb and resource: bringing a deleted entry back onto the public site. It also distinguishes this from the similar unmerge_entry sibling by explaining that merged entries must be handled there instead.

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

Usage Guidelines5/5

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

It gives clear when-to-use guidance for restoring a deleted entry and an explicit when-not-to-use case: merged entries that still redirect should use unmerge_entry. It also notes that the entry should be named by VHID because deleted entries have no public short name.

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.