Skip to main content
Glama
Sign In
CASDA MCP Server

CASDA MCP Server

by jbwod
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Search CASDA spectra

casda_search_spectra
Read-onlyIdempotent

Search for spectra in the CASDA archive by specifying position and optional band or time intervals to retrieve matching spectral data records.

Instructions

Discover spectra with the CASDA SSA interface.

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": {
      "ra_deg": "<ra_deg>",
      "dec_deg": "<dec_deg>",
      "size_deg": "<size_deg>"
    },
    "name": "casda_search_spectra"
  }
}

Input Schema

NameRequiredDescriptionDefault
bandNoOptional SSA BAND interval in metres.
timeNoOptional SSA TIME interval.
ra_degYesICRS right ascension in degrees, in [0, 360).
dec_degYesICRS declination in degrees, in [-90, 90].
size_degYesSSA SIZE search radius in degrees; server-bounded.
max_recordsNoMaximum rows to return; bounded by server configuration.

Output Schema

NameRequiredDescriptionDefault
errorNo
spectraNo
returnedYes
provenanceNo
max_recordsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, which cover safety traits. The description adds the SSA interface protocol but does not disclose other behaviors like pagination, result format, or server-side constraints beyond what schema provides.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence, but it lacks sufficient detail. While not verbose, it could include more information without harming conciseness.

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

Completeness2/5

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

Despite the presence of an output schema and high schema coverage, the description is minimal and does not explain the SSA interface or the search's scope. It is insufficient for a tool with many siblings and complex parameters.

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%, so parameters are fully documented. The tool description does not add any additional meaning beyond the schema; baseline score of 3 is appropriate.

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?

The description states 'Discover spectra' with a specific verb and resource, and mentions the CASDA SSA interface for context. However, it does not differentiate from sibling tools like casda_search_images or casda_search_catalogue, which also involve discovery.

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?

No guidance on when to use this tool versus alternatives (e.g., casda_create_spectrum, casda_search_images). No when-not or context exclusions provided.

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