Skip to main content
Glama
Sign In
paperless-mcp

paperless-mcp

by baruchiro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_correspondents

Retrieve all correspondents (document senders or receivers) with optional filtering and pagination.

Instructions

List all correspondents with optional filtering and pagination. Correspondents represent entities that send or receive documents.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_correspondents"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
orderingNo
page_sizeNo
name__iexactNo
name__icontainsNo
name__iendswithNo
name__istartswithNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.1
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. 'List' implies a read-only operation, but there is no explicit statement about safety, permissions, rate limits, pagination defaults, or what the response contains.

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 tightly written sentences with zero waste. The core purpose is front-loaded, followed by a brief clarifying definition.

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

Completeness2/5

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

For a 7-parameter list endpoint with no annotations, no output schema, and no schema descriptions, the description is too sparse. It omits parameter explanations, pagination behavior, filtering syntax, and return format details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 7 parameters at 0% description coverage, so the description must compensate. It only vaguely refers to 'filtering and pagination' without naming or explaining any of the specific name filters, ordering, page, or page_size parameters.

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?

States a specific verb ('List') and resource ('correspondents'), and adds a definition of what correspondents are. It implicitly distinguishes from single-item siblings like get_correspondent, but does not explicitly name alternatives or contrast with them.

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

Usage Guidelines2/5

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

Mentions optional filtering and pagination, which hints at capabilities, but provides no guidance on when to use this tool versus get_correspondent or other list tools, nor any conditions or prerequisites for filtering.

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