Skip to main content
Glama
Sign In
paperlessngx-mcp

paperlessngx-mcp

by Milli42
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

paperless_get_document_content

Retrieves the full OCR text of a document for reading, summarizing, or analyzing, only when explicitly requested.

Instructions

PRIVACY TIER 3: Returns FULL document content. The calling model will see the ENTIRE OCR text of this document. Only use this when the user has EXPLICITLY asked to read, summarize, or analyze a document's contents. For finding, organizing, or referencing documents, use the Tier 1 metadata tools instead. privacy_warning: This returns full document content into the model's context.

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": {
      "document_id": "<document_id>"
    },
    "name": "paperless_get_document_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
document_idYesPaperless document ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.6/5.0
Behavior5/5

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

Discloses PRIVACY TIER 3 and warns that full OCR text enters model context. No annotations to contradict; description adds crucial privacy context.

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?

Four concise sentences with front-loaded purpose and key information. No redundancy, every sentence adds value.

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?

Covers purpose, privacy, and usage guidelines adequately. Lacks mention of return format or error handling, but sufficient for a simple one-parameter tool.

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% for the single parameter 'document_id'. Description adds no extra parameter details beyond schema, achieving baseline.

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?

Explicitly states 'Returns FULL document content' and specifies usage for reading, summarizing, or analyzing documents. Clearly distinguishes from sibling metadata 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?

Provides explicit when to use (user asked to read/summarize/analyze) and when not to use (finding/organizing, refer to Tier 1 metadata tools).

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