Skip to main content
Glama

Coline

Restore from trash

restore_drive_file
Idempotent

Brings a file or folder back from trash.

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": {
      "workspace": "<workspace>",
      "fileId": "<fileId>"
    },
    "name": "restore_drive_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileIdYesFile or folder id from list_drive_files, search or fetch.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
restoredYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare the important traits: not read-only, idempotent, not destructive, not open-world. The description adds nothing beyond that — it does not say where the item is restored to (original parent vs. drive root), whether permissions are preserved, what happens if the item is not in trash, or whether special scopes are required.

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?

A single front-loaded sentence with no filler or redundancy. It is arguably too terse for a mutation tool, but no wording is wasted.

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

Completeness3/5

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

The tool is simple (two required params, full schema coverage, rich annotations, and an output schema that covers return values), so the description does not need to explain results. However, the one behaviorally significant unknown — where the restored item lands and whether conflicts are possible — is left unaddressed.

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 description coverage is 100%, so both parameters are already documented in the schema with sourcing hints (list_drive_files/search/fetch, workspaces.list). The description's only added nuance is "file or folder," which usefully signals that fileId accepts either type; otherwise it defers to the schema, making the baseline 3 correct.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Brings a file or folder back from trash"), which distinguishes it from most siblings. It does not name its inverse sibling trash_drive_file or otherwise contrast itself, but the action is unambiguous.

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

Usage Guidelines3/5

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

The phrase "back from trash" implicitly tells the agent the precondition (the item must already be trashed), which is real but minimal guidance. There is no explicit when-to-use/when-not statement and no mention of the inverse operation or of alternatives for permanently deleting or locating trashed items.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources