mcp-pcloud

pcloud_get_file_info

Retrieve metadata about any file in pCloud by providing its path. Get file size, modification dates, and more.

Instructions

Get metadata/information about a file in pCloud.

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

Input Schema

Name	Required	Description	Default
`path`	Yes	Path of the file

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

C2.9/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 for behavioral disclosure. It states 'Get' which implies a read operation, but does not disclose whether authentication is required, what specific metadata fields are returned, or any limitations. The description is too sparse to provide meaningful transparency.

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?

The description is a single sentence with no redundant words. It is front-loaded and appropriately sized for a simple tool, though it sacrifices useful detail for brevity. Every word earns its place, but the overall structure is minimal.

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?

There is no output schema, so the description should explain what information the agent will receive. It does not state the return format, the fields included in the metadata, or any error conditions. Given the tool's simplicity, this is a notable gap that leaves the agent uncertain about the tool's output.

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?

The input schema has 100% coverage with a single required parameter 'path' described as 'Path of the file'. The description adds no extra meaning beyond this. Since schema coverage is high, the baseline of 3 applies, but the description fails to enrich the parameter semantics further.

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?

The description clearly states the verb 'Get' and the resource 'metadata/information about a file in pCloud'. It distinguishes from siblings that perform actions (delete, rename, copy, create links) but is somewhat vague about what 'metadata' entails, making it less differentiated from tools like get_file_link or get_checksum.

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?

There is no guidance on when to use this tool versus alternatives. The description is declarative only and does not mention use cases, prerequisites, or exclusions. Since no information is provided, the agent must guess based on the tool name alone.

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

Deploy Server