Skip to main content
Glama
Sign In

Primavera

by com.primaverapp
OverviewDiscussionsAdmin

Download a file

get_list_file
Read-onlyIdempotent

Status of a prepared file. Once it is ready, "url" is a download link valid 120 seconds: download it at once or give it to the user, and call again for a new link.

Free.

Same call as GET /api/v1/lists/{id}/files/{fileId} of the REST API.

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": {
      "listId": "<listId>",
      "fileId": "<fileId>"
    },
    "name": "get_list_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileIdYesId of a prepared file (from prepare_list_file).
listIdYesId of a list of the account (from create_list or list_lists).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so safety is covered. The description adds genuinely non-obvious behavior: the URL expires after 120 seconds and a fresh call is required, plus the fact that the call is free — both are operational facts an agent could not derive from structured fields.

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?

Three short sentences, front-loaded with the state/URL semantics, followed by the cost signal and the REST endpoint mapping. Nothing is redundant and no sentence is filler.

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 only two required parameters, no nesting, and no output schema, the description carries the return-value burden reasonably by naming the "url" field and the ready state. It does not describe other possible status values or what a not-yet-ready response looks like, which is the remaining gap.

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?

Schema description coverage is 100% and both parameters already document their provenance (fileId from prepare_list_file, listId from create_list or list_lists). The description adds no additional constraint, format, or edge-case guidance beyond the schema, so the baseline of 3 applies.

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?

"Status of a prepared file" states the resource and the operation (status check / link retrieval) clearly, and the mention of the ready-state URL makes the outcome concrete. It does not explicitly contrast with siblings like get_job or prepare_list_file, but the pairing with prepare_list_file is implied through the fileId origin.

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?

It tells the agent what to do with the result ("download it at once or give it to the user, and call again for a new link"), which effectively documents the poll-then-download workflow. What is missing is an explicit statement of when to call it (e.g., only after prepare_list_file returns, or while status is pending), leaving that sequencing to inference.

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

All Primavera toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources