Skip to main content
Glama
Sign In
Paperless MCP

Paperless MCP

by pvliesdonk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

List Storage Paths

list_storage_paths
Read-onlyIdempotent

List all storage paths configured in Paperless-NGX to identify available locations for document filing and retrieval.

Instructions

List storage paths.

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_storage_paths"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
orderingNo
page_sizeNo

Output Schema

NameRequiredDescriptionDefault
nextNo
countYes
resultsNo
previousNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

D1.6/5.0
Behavior1/5

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

The description adds no behavioral context beyond what annotations already provide (readOnly, idempotent, non-destructive). It does not mention pagination behavior, ordering, or return format, leaving the agent uninformed about operational details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short, but this is under-specification rather than conciseness. It omits essential information that should be present for a tool with pagination parameters.

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

Completeness1/5

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

For a tool with three parameters and no schema descriptions, the description provides no usage guidance, parameter explanation, or behavioral context. The existence of an output schema does not compensate for the lack of operational information.

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

Parameters1/5

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

Schema coverage is 0% and the description does not explain any of the three parameters (page, ordering, page_size). The agent receives no semantic guidance beyond the parameter names.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear verb and resource ('List storage paths'), but it is minimal and does not differentiate from siblings like get_storage_path or other list tools. It lacks any context about what storage paths are or how they relate to other resources.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool versus alternatives. No mention of pagination, filtering, or when get_storage_path would be more 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