Skip to main content
Glama

Export a document to a folder

export_doc
Idempotent

Copies a document to Markdown files in an existing folder, with pages numbered in reading order and files beside them. Export a snapshot without changing the original.

Instructions

Write a document out as Markdown files in a folder on this machine, its pages numbered in reading order and its files beside them. A copy: nothing here changes. For another tool, read_doc with as.

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": {
      "doc": "<doc>",
      "into": "<into>"
    },
    "name": "export_doc"
  }
}

Input Schema

NameRequiredDescriptionDefault
docYesThe document's id from `docs`, not its title
intoYesAn existing folder under Downloads, Documents, Pictures, Desktop or the temporary folder, not used for this document before

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.43.2
    • changedInput schema / properties / doc / description
      Previous value: -"The document's id, as `docs` hands it back — an opaque name like `q7ntmzbm-0001`, not its title"New value: +"The document's id from `docs`, not its title"
    • changedInput schema / properties / into / description
      Previous value: -"A folder that exists on this machine, which an export of this document has not been taken to already: one is made inside it, named after the title, under Downloads, Documents, Pictures, Desktop or the temporary folder"New value: +"An existing folder under Downloads, Documents, Pictures, Desktop or the temporary folder, not used for this document before"
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=false and idempotentHint=true, and 'A copy: nothing here changes' usefully reinforces that the source document is untouched. It adds the output shape (numbered pages, sidecar files) but says nothing about what happens if the target folder is already populated, what the tool returns on success, or failure behavior — notable given readOnlyHint=false means it does write to disk.

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?

Three short sentences, front-loaded with the action and scope, with no filler. The trailing fragment 'For another tool, `read_doc` with `as`' is awkwardly worded and slightly opaque, which costs it the top score.

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?

With no output schema and a two-parameter surface, the description covers the essentials: it writes Markdown files, numbers pages, places attachment files alongside, and does not modify the source. It leaves post-condition details (existing folder contents, error cases) unstated, which keeps it short of a 5.

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 coverage is 100% and both parameters are fully documented in the schema, including the 'not used for this document before' constraint. The description adds no meaning about `doc` or `into`; its extra detail concerns output layout rather than parameter semantics, so baseline 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: writes a document out as Markdown files into a folder on this machine, with pages numbered in reading order and attachments placed beside them. It also names the sibling it is not (read_doc), so an agent can distinguish it 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?

It routes the agent to read_doc 'with `as`' for the non-export case, which is a real alternative pointer. However, that final sentence is grammatically truncated and never states when *not* to export or what the preconditions are beyond the schema's folder rule.

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