Skip to main content
Glama
Pandafile MCP Server

Pandafile MCP Server

Official
by pandafileco

Account, plan and usage

get_account
Read-onlyIdempotent

Fetches account plan, limits, usage, storage, and test-key status for the current API key, helping verify quotas and available features.

Instructions

The account behind the API key: plan, limits (max bytes per transfer, expiry days, features), usage (this week / month, storage) and whether the key is a test key.

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": "get_account"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value beyond that by scoping the call to the identity of the API key (i.e., no account identifier needed) and by disclosing the shape of what comes back, including the test-key flag — useful since there is no output schema.

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?

A single dense sentence with the resource front-loaded and the returned facets grouped parenthetically. Every clause carries information; there is no filler or repetition of the title.

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?

With no output schema, the description must carry the return-value burden, and it does so by enumerating plan, limits, usage windows, storage, and test-key status. Slight gaps remain (e.g., exact units or reset cadence for the weekly/monthly usage), but an agent has enough to decide to call it and interpret the result.

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 takes zero parameters, so there is nothing for the description to disambiguate. Baseline for a parameterless tool is 4; the description correctly conveys that the account is derived from the API key rather than passed in.

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 names the exact resource ('The account behind the API key') and enumerates its contents: plan, limits (max bytes per transfer, expiry days, features), usage (week/month, storage), and test-key status. That is far more specific than a restatement of the name. It does not explicitly contrast with any sibling, but none of the listed siblings (transfer/file-request operations) overlap, so ambiguity is low.

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

Usage Guidelines3/5

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

There is no explicit 'use this when...' statement or exclusion. Usage is only implied by the content list — an agent would infer it should call this to discover plan limits before sending files, or to check whether the key is a test key. The inference is reasonable but not stated.

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