Skip to main content
Glama
Sign In
mcp-paperless-ngx

mcp-paperless-ngx

by tobee89
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Update storage path

update_storage_path

Update only the chosen attributes of a storage path, such as name, path template, matching rule, or permissions, leaving unspecified fields unchanged.

Instructions

Partially update a storage path. Only the fields you pass are changed; omitted fields keep their current value.

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": {
      "id": "<id>"
    },
    "name": "update_storage_path"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
nameNo
pathNoFilename template, e.g. '{created_year}/{correspondent}/{title}'. Required when creating.
matchNoText this object matches against, interpreted per matching_algorithm.
ownerNoOwning user ID, or null for unowned.
is_insensitiveNoCase-insensitive matching. Defaults to true.
set_permissionsNoObject-level permissions. Overwrites existing permissions entirely unless the endpoint supports merging.
matching_algorithmNoMatching algorithm: 0=none, 1=any word, 2=all words, 3=exact, 4=regex, 5=fuzzy, 6=auto. Use 6 (auto) unless the user asked for a specific rule.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.9/5.0
Behavior4/5

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

The sentence 'Only the fields you pass are changed; omitted fields keep their current value' reveals important merge behavior not captured by annotations. It complements the annotation profile (readOnlyHint=false) and adds value by explaining the update semantics.

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?

The description is two short sentences, front-loaded with the core action and followed immediately by the most important behavioral qualifier. Every sentence earns its place with no filler.

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?

The description covers partial-update semantics but says nothing about return values, errors, or authorization requirements, and there is no output schema to fill that gap. The schema handles parameters well, so this is adequate for a CRUD update but not complete.

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 75%, and the schema already documents the parameters well, including path templates, matching_algorithm values, and permissions behavior. The tool description adds no parameter-level guidance, so the baseline of 3 applies.

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?

The description opens with 'Partially update a storage path,' which states a specific verb, resource, and semantic nuance. This clearly distinguishes it from sibling tools like create_storage_path, delete_storage_path, get_storage_path, and test_storage_path.

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?

The description implies use when modifying an existing storage path and clarifies partial-update semantics, but it never names alternatives or states when not to use this tool. It lacks explicit routing guidance versus create_storage_path or other storage-path operations.

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