Skip to main content
Glama
Sign In
CASDA MCP Server

CASDA MCP Server

by jbwod
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Inspect CASDA DataLink

casda_get_datalink
Read-onlyIdempotent

Retrieve DataLink access descriptors for a CASDA product, listing service names, content types, and sizes.

Instructions

Inspect DataLink access descriptors for one product.

Returns service names, content types, and sizes. Opaque authenticated ID tokens are redacted and never returned.

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_get_datalink"
  }
}

Input Schema

NameRequiredDescriptionDefault
product_idYesExact CASDA product identifier to inspect via DataLink.

Output Schema

NameRequiredDescriptionDefault
errorNo
servicesNo
product_idYes
provenanceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds value by disclosing that authenticated ID tokens are redacted and never returned, which is a key behavioral trait not captured by annotations.

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 sentences with no wasted words. The first sentence states the action, the second specifies return values and a key behavioral note. Information is front-loaded and essential.

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 simplicity (one parameter, read-only, with an output schema), the description fully covers what it does and what it returns. No additional context is needed.

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?

The sole parameter product_id has full schema coverage with a clear description. The tool description adds minimal extra meaning beyond reinforcing that it inspects one product. Baseline of 3 is appropriate.

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 specifies the verb 'Inspect', the resource 'DataLink access descriptors', and the scope 'for one product'. It uniquely identifies the tool's function among siblings, as no other tool mentions DataLink.

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?

The description implies when to use the tool (when needing DataLink access descriptors) but does not explicitly state when not to use it or mention alternatives like casda_get_product or casda_download_product.

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