Skip to main content
Glama

Put documents in a folder

file_doc
Idempotent

Move documents by ID into an existing folder, or remove them from all folders by omitting the folder; archived documents stay archived.

Instructions

Move documents into a folder, or out of every folder by leaving folder out. Only the place changes; an archived document moves and stays put away.

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>"
    },
    "name": "file_doc"
  }
}

Input Schema

NameRequiredDescriptionDefault
docYesThe id of the document to file, not its title, or a list of ids: if one cannot, none moves
folderNoAn existing folder, by name, path or id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.43.2
    • changedInput schema / properties / doc / description
      Previous value: -"The id of the document to file, as `docs` hands it back — an opaque name like `q7ntmzbm-0001`, not its title. A list of ids does the same to all of them in one go, and if one of them cannot, none of them moves."New value: +"The id of the document to file, not its title, or a list of ids: if one cannot, none moves"
    • changedInput schema / properties / folder / description
      Previous value: -"An existing folder, by its name, its whole path or its id. Leave it out to take the document out of every folder"New value: +"An existing folder, by name, path or id"
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare idempotent, non-destructive, non-read-only behavior, so the bar is lower. The description contributes non-obvious semantics: only placement changes and an archived document 'moves and stays put away', telling the agent the operation neither edits content nor restores archived documents.

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 sentences, no filler, with the primary action and the omit-parameter sidestep front-loaded. Each clause carries distinct information (destination, unfiling, non-destructiveness, archive preservation).

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 only two fully documented parameters, no output schema, and clear annotations, the definition covers what an agent needs to invoke it correctly. Minor gap: it doesn't say what happens if `folder` doesn't exist or what the response looks like, though the schema's 'An existing folder' wording hints at the former.

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 100%, so the schema already explains `doc` semantics including the all-or-nothing list behavior. The description still adds value the schema lacks: omitting `folder` means removal from every folder, which is not stated anywhere in the input schema.

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?

The description pairs a concrete verb ('Move documents') with a concrete resource and destination ('into a folder'), and it clarifies the inverse case ('out of every folder'). It does not name an overlapping sibling such as 'move' or 'folder', so the agent must still infer the boundary, but the verb+resource 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 Guidelines4/5

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

It gives a clear selection rule for the optional parameter: supply `folder` to file, omit it to remove from all folders. What's missing is any reference to alternatives ('move' or 'folder' siblings) when the intent is something other than filing, so the when-not guidance is only partial.

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