Skip to main content
Glama
Sign In

Typebar (formerly SuperDocs)

by ai.typebar
OverviewDiscussionsAdmin

unarchive_document

Restore (un-archive) a saved document by its id — the mirror of archive_document. The document re-enters your Files view and can be opened/edited again (open it into a chat with open_documents). document_id is the same id used by list_documents / archive_document. Idempotent: restoring an already-active (or unknown) document is a no-op. Non-billable.

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": {
      "document_id": "<document_id>"
    },
    "name": "unarchive_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
document_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / authorization
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "title": "Authorization"
-}
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

With zero annotations the description carries the full burden and does so: it discloses the state effect (document re-enters Files view and becomes editable), idempotency semantics ('no-op' on already-active or unknown ids), and cost profile ('Non-billable'). These are exactly the traits an agent needs to reason about calling a mutation safely.

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 action and the archive_document relationship, then layers the side effect, parameter provenance, idempotency and billing in compact clauses. Slightly dense with parentheticals but every clause carries distinct information; nothing is padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter mutation with no annotations and no output schema, the description covers effect, idempotency, cost, and parameter sourcing. The one remaining gap is the return value (what the agent gets back on success vs. the no-op case), which has no schema to defer to.

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 0% and the single parameter has no description, so the description must compensate — it does by defining the id's provenance ('the same id used by list_documents / archive_document'), which tells the agent where to obtain a valid value. It doesn't give format examples (UUID vs. slug), keeping it off a 5.

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+resource ('Restore (un-archive) a saved document by its id') and immediately distinguishes itself from the sibling archive_document as its mirror operation. An agent can pick it over archive_document or open_documents 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?

Clearly frames the usage context (bring a document back into the Files view) and routes forward to open_documents for the natural next action, plus notes that restoring an already-active document is a no-op. No explicit 'when not to use' beyond that idempotency note, so it falls just short of a 5.

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

All Typebar (formerly SuperDocs) toolsInspect
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