Skip to main content
Glama
Sign In
mcp-pcloud

mcp-pcloud

by fatherlinux
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

pcloud_read_text_file

Read a text file from pCloud by providing its path and receive the file's contents for use in your workflow.

Instructions

Read the contents of a text file from 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_read_text_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesPath of the text file to read

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/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 of behavioral disclosure, but it only says 'read contents' without detailing error handling, return format, permissions, or file type support. This lack of context could lead to incorrect assumptions about edge cases.

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 a single, front-loaded sentence that efficiently states the tool's purpose without redundancy. Every word earns its place.

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

Completeness4/5

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

For a simple one-parameter read operation, the description and schema convey the essential purpose. However, given the absence of an output schema and annotations, a brief note on return format or error behavior would improve completeness, but the current level is nearly sufficient.

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 schema fully covers the single path parameter with a clear description ('Path of the text file to read'), achieving 100% coverage. The description adds no additional parameter information, so the baseline score of 3 is appropriate.

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 clearly states a specific action (read) and resource (text file from pCloud), distinguishing it from sibling tools that handle metadata, deletion, renaming, or linking. It is unambiguous and directly reflects the tool's function.

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 guidance is provided on when to use this tool versus alternatives like pcloud_get_file_info or pcloud_get_file_link. The description does not mention prerequisites, exclusions, or typical usage scenarios, leaving the agent to infer context from the 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

Other Tools