Azquo

Restore deleted name

restore_name

Bring back a deleted name (ids from list_deleted_names or name_history). It returns as a NEW name with a new id, its attributes as they were when deleted, put back in the sets it was in and given back its children - where those still exist. Its VALUES ARE NOT RESTORED: deleting a name deletes its values. The response counts what was relinked and what could not be. The restore's provenance records the old id, so the two histories can be followed.

═══ PROVENANCE — required on every write ═══ source: why the name is being restored. agent: your AI agent name (e.g. "Claude").

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": {
      "database": "<database>",
      "nameId": "<nameId>",
      "source": "<source>",
      "agent": "<agent>"
    },
    "name": "restore_name"
  }
}

Input Schema

Name	Required	Description
`agent`	Yes	AI agent name (e.g. "Claude"). REQUIRED.
`nameId`	Yes	Id the name had before it was deleted
`source`	Yes	Why it is being restored - ticket, note or document. REQUIRED.
`business`	No	Optional. The business this call is for, by name, e.g. "azquo" - it then runs there whatever business the session is in. Worth giving on writes when you work in more than one business: a new MCP session starts in the login's own business. list_businesses shows the names.
`database`	Yes	Database name

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 21, 2026

addedInput schema / properties / business

Added value: +{
+  "description": "Optional. The business this call is for, by name, e.g. \"azquo\" - it then runs there whatever business the session is in. Worth giving on writes when you work in more than one business: a new MCP session starts in the login's own business. list_businesses shows the names.",
+  "type": "string"
+}

First observedOct 19, 2026

TDQS

A4.6/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 the restored name gets a NEW id, that attributes return as they were at deletion, that set memberships and children are relinked only "where those still exist", that VALUES ARE NOT RESTORED, and that the response counts relinked vs. failed items. These are exactly the consequences an agent needs before mutating.

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-loads the restore semantics and the most important caveat (values not restored) before the provenance block. The provenance section partially duplicates the schema field descriptions and the box-drawing header is noisy, but overall it is dense rather than padded.

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 mutation tool with no output schema, it describes both side effects and the shape of the response (counts of what was relinked and what could not be), plus provenance traceability back to the old id. Nothing an agent needs to call this correctly is missing.

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 real meaning: nameId is the pre-deletion id and is obtainable from list_deleted_names/name_history, and source/agent are framed as mandatory provenance on every write. The business parameter's semantics remain schema-only.

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?

Opens with a specific verb+resource ("Bring back a deleted name") and immediately distinguishes itself from delete_name/edit_name_attributes by naming the sibling sources of the id. An agent can tell what this does and where the input comes from without opening a 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?

Gives the prerequisite for use (ids come from list_deleted_names or name_history) and states the required provenance fields for every write. It does not spell out when *not* to restore or compare against alternative recovery paths, so it stops short of full when/when-not routing.

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

All Azquo 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.

Resources

Need Help?