Skip to main content
Glama
Sign In
mcp-pcloud

mcp-pcloud

by fatherlinux
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

pcloud_get_user_info

Retrieve account details and quota usage for the authenticated pCloud user, enabling monitoring of storage capacity and resource management.

Instructions

Get information about the authenticated pCloud user, including quota usage.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pcloud_get_user_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. The verb 'Get' implies a read-only operation, and the mention of 'authenticated user' indicates authentication is involved. However, it doesn't explicitly state that no changes are made or describe any potential side effects, leaving some ambiguity.

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, direct sentence that immediately conveys the core purpose. It is concise and front-loaded, with no unnecessary words.

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 tool with no parameters, no annotations, and no output schema, the description is sufficient in scope. It names the resource (user info) and a key detail (quota usage), which covers the essential use case. However, it could be more complete by listing other possible returned fields, but this is not critical given the tool's simplicity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so the description need not explain parameter usage. The baseline for 0 params is 4, and the description appropriately makes no redundant parameter references.

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 the tool's function: to get information about the authenticated pCloud user, specifically mentioning quota usage. This distinguishes it from sibling tools that focus on files and folders.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context: it is used to retrieve user account information. While it doesn't explicitly mention alternatives, the sibling tools are all file/folder operations, so the usage is unambiguous. No exclusion criteria are needed.

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