Skip to main content
Glama

Download a research project delivery

download_delivery

Save a research project’s delivered version—latest unless a version is specified—as a ZIP in a chosen directory and return the file path.

Instructions

Save a delivered version of a research project (the latest unless version is given) as a zip in a directory, and return its path. Free.

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": {
      "project_id": "<project_id>",
      "directory": "<directory>"
    },
    "name": "download_delivery"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionNoThe delivered version; the latest by default
directoryYesAbsolute path of the directory to save the zip in
project_idYesThe project id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.7.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only say it is not read-only and not destructive; the description adds that a file is written into a caller-supplied directory, that the latest version is picked unless version is given, that the return value is the resulting path, and that the call is free. Missing only overwrite/failure behavior if the zip already exists.

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?

One sentence with the effect front-loaded, the version default parenthesized inline, and the output path stated before the trailing cost note. Nothing extraneous.

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 3-parameter tool with no output schema, the description covers what is produced (a zip) and what is returned (its path), plus cost. Side-effect details such as filename or overwrite handling are the only 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 coverage is 100% and the schema already documents all three parameters, including 'the latest by default' for version and 'absolute path' for directory. The description restates the version default rather than adding new meaning, so the baseline 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?

States a specific verb ('Save') and resource ('a delivered version of a research project ... as a zip') plus the return value (its path). It is clearly distinguishable from the sibling job/project tools, though it never names an alternative explicitly.

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?

Usage is implied by 'delivered version' – the agent can infer this applies after a delivery exists – but there is no explicit when-to-use/when-not-to-use guidance or prerequisite statement relative to act_on_project, wait_for_project, or check_job.

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