mcp-pcloud-crunchtools

Pcloud Get Checksum

pcloud_get_checksum

Read-only

Retrieve stored SHA256, SHA1, and MD5 checksums for a specified pCloud file to verify integrity or detect changes.

Instructions

Get pCloud's stored SHA256, SHA1, and MD5 checksums for a file.

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

Input Schema

Name	Required	Description	Default
`path`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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

B3/5.0

Behavior3/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. The description adds one genuinely useful behavioral detail beyond the annotation: the checksums are 'pCloud's stored' values, implying server-side hashes rather than locally computed ones. It says nothing about permissions or whether checksums may be absent for some files, so with annotations already covering the safety profile a 3 is right.

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?

One tight sentence with no filler, and the operation and its return payload are front-loaded. It is efficient, though it spends none of its budget on the guidance the definition lacks.

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?

An output schema exists, so return values need not be explained. However, with zero schema coverage on the only parameter, the undefined path semantics leave a real gap for a tool whose entire input is that one path.

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% for the single required 'path' parameter. The description only implies 'for a file' and never clarifies whether path is root-relative, absolute, or includes a filename, so it fails to compensate for the schema's silence.

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 ('Get') and a specific resource ('SHA256, SHA1, and MD5 checksums for a file'), which is more precise than the sibling pcloud_get_file_info's generic metadata framing. It does not explicitly name or contrast a sibling, so it stops short of a 5.

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?

No when-to-use guidance, no condition for preferring this over pcloud_get_file_info (which plausibly also surfaces file metadata), and no prerequisites. The agent must infer the usage context entirely.

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

Deploy Server