Skip to main content
Glama
Sign In

Clarifo

by com.clarifo
OverviewDiscussionsAdmin

restore_from_trash

Idempotent

Bring a document or note back from Clarifo's trash, with its versions, comments and company links, when the user asks. Find it with list_workspace_items(in_trash=true).

Args: idempotency_key: Optional; leave it out. Clarifo recognises a repeated identical request by its content. Give one only to retry this same request. item_id: A document in the trash. note_id: A note in the trash.

Returns: {"status": "restored", "kind", "item_id" | "note_id", "title", "editor_url" | "note_url"} or {"error", "failure_kind"}.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "restore_from_trash"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_idNo
note_idNo
idempotency_keyNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the annotations (which already mark it non-read-only, idempotent and non-destructive), the description discloses what is restored alongside the item and explains the idempotency-key mechanism (repeated identical requests recognised by content; supply only to retry). It also names the failure return shape. Minor gap: no statement about what happens if the id is not actually in trash.

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-loaded purpose sentence followed by compact Args and Returns blocks; every line is useful. The idempotency_key explanation is slightly wordier than needed but still earns its place given the unusual semantics.

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?

Covers the trigger, the id-discovery prerequisite, all parameters, and the success/error return shapes, so an agent can call it correctly. The Returns block is partly redundant with the output schema, and mutual exclusivity of item_id/note_id is the one missing decision rule.

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%, so the description carries the burden, and it documents all three parameters: idempotency_key (optional, normally omit), item_id (a document in the trash), note_id (a note in the trash). It stops short of stating that exactly one of item_id/note_id should be supplied.

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 ("Bring a document or note back from Clarifo's trash") and adds scope detail — versions, comments and company links come back with it. It is clearly distinguishable from move_to_trash and list_workspace_items.

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 an explicit trigger ("when the user asks") and a concrete discovery path: find the id via list_workspace_items(in_trash=true). It does not say what to do when the id is unknown/stale or how to choose between item_id and note_id, but the key routing guidance is present.

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

All Clarifo 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