Skip to main content
Glama

Files File Upload

files_file_upload

Retrieve registration and destination details for a file upload via the Pingen API without transferring file bytes.

Instructions

Get details for file upload (upload registration/destination etc). GET /file-upload

Registration metadata only: the server never proxies file bytes, so the JSON:API response passes through unchanged. The optional fields_file_uploads argument maps to the query parameter fields[file_uploads] (which attributes of file_uploads to return) and is omitted from the request when not given.

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

Input Schema

NameRequiredDescriptionDefault
fields_file_uploadsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose meaningful behavior: the server never proxies file bytes and the JSON:API response passes through unchanged. It omits whether this returns a single registration or a collection, whether authentication/workspace scoping applies, and any pagination behavior, which are notable gaps for a read endpoint.

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?

Three sentences, front-loaded with the purpose and followed by behavioral and parameter detail in a sensible order. The 'GET /file-upload' fragment is borderline boilerplate but conveys the underlying endpoint, and no sentence is repeated filler.

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?

For a single optional parameter with no annotations or output schema, the description covers the parameter well and hints at response shape ('JSON:API response passes through unchanged'). It is still ambiguous whether a single upload registration or a collection is returned, leaving the agent uncertain about the result to expect.

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?

Schema coverage is 0% and the parameter name is cryptic, but the description fully compensates: it explains that fields_file_uploads maps to the query parameter fields[file_uploads], controls which attributes are returned, and is omitted from the request when not supplied. That is exactly the meaning an agent needs.

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 and resource ('Get details for file upload') and scopes it to registration/destination metadata, which is clearer than the bare tool name. It does not explicitly distinguish itself from any sibling, though none of the listed siblings appear to be a file-upload lookup, so confusion risk 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 Guidelines2/5

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

The description never says when to call this versus another tool, nor what prerequisites exist. The only scoping signal is the negative one ('registration metadata only'), which tells the agent what it will not get but not when this is the right call.

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