mcp-pcloud-crunchtools

Pcloud Search

pcloud_search

Read-only

Search pCloud storage for files and folders whose names match a query within a specified path. Use it to locate items in your cloud drive by name instead of browsing folders manually.

Instructions

Search pCloud for files and folders whose names match a query.

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": {
      "query": "<query>",
      "path": "<path>"
    },
    "name": "pcloud_search"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes
`query`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv3.0.1Oct 17, 2026
- removedInput schema / properties / path / default
```
Removed value: -"/"
```
- changedInput schema / required
```
Previous value: -[
-  "query"
-]New value: +[
+  "query",
+  "path"
+]
```
Changed2 schema fields changedv2.5.0Sep 22, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- removedOutput schema / description
```
Removed value: -"Generic wrapper for non-object return types."
```
First observedv2.1.0Sep 8, 2026

TDQS

C2.7/5.0

Behavior2/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description needs to add context such as result caps, recursion scope, or pagination. It adds nothing beyond confirming 'search', leaving behavior largely undisclosed.

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

Conciseness4/5

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

A single front-loaded sentence with no waste and no filler. It is efficient, though the brevity comes at the cost of the detail the parameters need.

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?

The output schema covers return values, but the description leaves the required 'path' parameter, recursion scope, result limits, and any usage conditions completely unexplained for a two-required-parameter tool.

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?

Schema description coverage is 0%, so the description carries the full burden, yet it only gestures at 'query' and never explains what 'path' means (search root? must it exist? is matching recursive within it?). With two required parameters and no schema text, this is a real gap.

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 (Search) and resource (pCloud files and folders) with the matching criterion (names match a query). It distinguishes itself implicitly from pcloud_list_folder by specifying name matching rather than enumeration, but never names a sibling or clarifies the boundary.

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?

The description gives no when-to-use guidance, no indication of when to prefer pcloud_list_folder or pcloud_get_file_info instead, and no mention of prerequisites such as authentication or whether the search is recursive.

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

Deploy Server