Skip to main content
Glama

Docflare

Archive a draft

archive_document

Moves a draft the user no longer wants to the trash in Docflare, where they can restore it. Only drafts: a sent document stays.

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": {
      "id": "<id>"
    },
    "name": "archive_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe id of the draft, from document_status or an earlier answer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations say readOnlyHint=false and destructiveHint=false, and the description explains why the operation is non-destructive: the item goes to the trash 'where they can restore it.' That reversibility detail is real added value. It does not mention permissions or what happens when a non-draft id is passed, so it is not a 5.

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?

Two short sentences, front-loaded with the action, followed by the scope constraint. No filler and nothing repeated from the schema or annotations.

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 annotations and no output schema, the description covers the key facts: destination (trash), reversibility (restorable), and scope (drafts only). It omits error behavior for non-draft ids and whether confirmation is required, which are the only meaningful remaining gaps.

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?

Only one parameter and schema description coverage is 100%, so the schema already documents the id and where to obtain it ('from document_status'). The description conveys that the id must refer to a draft but adds no format or validation detail beyond the schema, so the baseline of 3 applies.

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 ('Moves a draft ... to the trash') plus the exact scope ('Only drafts: a sent document stays'), which is enough to separate it from send_document and edit_document without opening either 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?

The condition is explicit: use it for a draft 'the user no longer wants,' and the exclusions are stated ('Only drafts: a sent document stays'). It doesn't name a sibling as the alternative or mention restoring as a follow-up, so it stops short of a full 5.

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