Skip to main content
Glama
Sign In
CASDA MCP Server

CASDA MCP Server

by jbwod
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Download CASDA product

casda_download_product
Idempotent

Download a confirmed-ready CASDA product with guarded streamed writes, byte limit enforcement, and optional checksum verification, without overwriting existing files.

Instructions

Download one confirmed-ready product using guarded, streamed local filesystem writes.

This operation requires CASDA_ENABLE_DOWNLOADS and a restricted CASDA_DOWNLOAD_DIR. It never overwrites by default, enforces the byte limit, verifies Content-Length, resumes within the call when Range is supported, and removes incomplete files after failure.

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": {
      "product_id": "<product_id>"
    },
    "name": "casda_download_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
product_idYesOne explicit CASDA product identifier confirmed ready by staging.
destinationNoOptional path constrained to CASDA_DOWNLOAD_DIR; defaults to the archive filename.
verify_checksumNoVerify the archive checksum when a checksum sidecar is available.

Output Schema

NameRequiredDescriptionDefault
errorNo
resultNo
provenanceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

The description goes well beyond annotations by detailing behaviors: never overwrites by default, enforces byte limit, verifies Content-Length, resumes on Range support, removes incomplete files after failure. This provides essential safety context for a file download operation.

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?

Two short, front-loaded sentences covering purpose and key behaviors. Every sentence adds information; no fluff. Highly efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (download with options) and the presence of an output schema, the description covers prerequisites, safety, and behavioral quirks comprehensively. It is sufficient for an agent to use correctly.

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 covers 100% of parameters with good descriptions. The description adds clarity on constraints (destination constrained to CASDA_DOWNLOAD_DIR) and default behavior (verify_checksum default true). This adds value beyond the schema.

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 action: 'Download one confirmed-ready product using guarded, streamed local filesystem writes.' It uses specific verb+resource and distinguishes from sibling tools like casda_get_product (which likely returns metadata) and staging tools.

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 mentions prerequisites ('requires CASDA_ENABLE_DOWNLOADS and a restricted CASDA_DOWNLOAD_DIR') and implies the product must be confirmed-ready (via staging). It does not explicitly list alternatives or when-not-to-use, but the context of sibling tools provides differentiation.

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