Skip to main content
Glama
Sign In
mcp-document-intelligence

mcp-document-intelligence

by AndreasDietzel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

process_downloads

Scan and analyze documents in a downloads folder, then sort them into an archive. Use auto-move or preview mode to review changes before files are moved.

Instructions

Scan the downloads folder, analyze documents, and sort them into an archive. Supports auto-move or preview mode.

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": {
      "archiveBasePath": "<archiveBasePath>"
    },
    "name": "process_downloads"
  }
}

Input Schema

NameRequiredDescriptionDefault
autoMoveNoAuto-move files (default: false = preview only)
maxFilesNoMax files to process (default: 50)
downloadsPathNoPath to downloads folder (default: ~/Downloads)
archiveBasePathYesTarget archive folder

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.6.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden for a tool that can move files into an archive. It says auto-move exists but never states whether originals are removed or copied, whether the archive structure is created, whether conflicts overwrite, or that an auto-move run is effectively irreversible. For a mutation-capable tool with zero annotation coverage this is a significant gap.

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?

Two short sentences, front-loaded with the pipeline and followed by the mode distinction. Nothing is wasted, though the second sentence could have been spent on more valuable behavioral disclosure.

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?

With no annotations and no output schema, the description must cover both safety and result interpretation, and it does neither fully. Preview mode is offered but the description never says what a preview returns (a plan? a list? nothing?), which leaves the agent guessing how to report results.

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 all four parameters including defaults are already documented, and the baseline is 3. The description's phrase 'auto-move or preview mode' reinforces the meaning of autoMove but adds no syntax, path, or limit detail beyond the 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 names specific verbs and a resource: scan the downloads folder, analyze documents, sort into an archive. That is far more concrete than the tool name alone. It does not, however, distinguish this composite pipeline from siblings like batch_organize, auto_organize, or scan_directory, so an agent cannot tell from the text alone why it should pick this one.

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?

'Supports auto-move or preview mode' implies the safe default is preview, which is useful usage context. But there is no explicit when-to-use versus the many siblings, no prerequisites named, and no statement of when preview versus auto-move is appropriate.

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

Deploy Server

Other Tools