Paperless MCP

Get Document

get_document

Read-onlyIdempotent

Retrieve document metadata by ID, excluding OCR content to keep responses small. For full text, use get_document_content or create a download link.

Instructions

Fetch one document by ID.

OCR content is stripped to keep responses small. Call get_document_content for a bounded preview, or use create_download_link with the content variant when available.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`document_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`tags`	No
`added`	No
`notes`	No
`owner`	No
`title`	Yes
`content`	No
`created`	Yes
`web_url`	No
`modified`	No
`page_count`	No
`created_date`	No
`storage_path`	No
`correspondent`	No
`custom_fields`	No
`document_type`	No
`user_can_change`	No
`archived_file_name`	No
`original_file_name`	No
`archive_serial_number`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.1.0Sep 21, 2026
- removedInput schema / properties / include_content
```
Removed value: -{
-  "default": false,
-  "type": "boolean"
-}
```
First observedv1.0.1Jul 8, 2026

TDQS

A4.5/5.0

Behavior3/5

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

Annotations already cover safety: readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false. The description adds a useful behavioral detail beyond annotations: OCR content is stripped to keep responses small. It does not go into error handling or authorization, so 3 is appropriate.

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?

Three short sentences with no filler. The core action is front-loaded, and the following two sentences add only targeted routing details that an agent genuinely needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With one required integer parameter, an output schema present, and annotations covering read-only/idempotent behavior, nothing critical is missing. The content-related alternatives are explicitly named, so an agent can decide correctly without guessing.

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?

The only parameter is document_id, an integer with no schema description (0% coverage). The phrase 'by ID' directly links the parameter to the fetch operationcars; for a single self-explanatory parameter, this is sufficient meaning beyond the raw schema.

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 clear action and resource: 'Fetch one document by ID.' It also distinguishes the tool from content-focused siblings by noting 'OCR content is stripped' and pointing to get_document_content, so an agent can tell this apart from related get_document_* tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly routes alternative usage: 'Call get_document_content for a bounded preview, or use create_download_link with the content variant when available.' This tells the agent when to prefer a different tool instead of get_document.

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

Deploy Server