Skip to main content
Glama
Sign In
CASDA MCP Server

CASDA MCP Server

by jbwod
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Search CASDA survey images

casda_search_survey_images
Read-onlyIdempotent

Locate survey images from ASKAP data archive by specifying survey, coordinates, and search size.

Instructions

Discover survey images with the CASDA SIA 1 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": {
      "survey": "<survey>",
      "ra_deg": "<ra_deg>",
      "dec_deg": "<dec_deg>",
      "size_deg": "<size_deg>"
    },
    "name": "casda_search_survey_images"
  }
}

Input Schema

NameRequiredDescriptionDefault
ra_degYesICRS right ascension in degrees, in [0, 360).
surveyYesSurvey code from casda_list_image_surveys, such as RACS-Low.
dec_degYesICRS declination in degrees, in [-90, 90].
size_degYesSIAP1 SIZE search box in degrees; server-bounded.
max_recordsNoMaximum rows to return; bounded by server configuration.

Output Schema

NameRequiredDescriptionDefault
errorNo
imagesNo
returnedYes
provenanceNo
max_recordsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the description adds minimal behavioral context beyond mentioning the SIA 1 interface. It does not contradict annotations.

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

Conciseness4/5

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

The description is a single, concise sentence. It is front-loaded and wastes no words, but could be slightly more informative without losing 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 having an output schema, the description lacks context about the result format, limitations, or typical use cases. More guidance would be needed for effective use.

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 descriptions are detailed. The tool description adds no additional parameter semantics beyond what is already in the input schema.

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 the tool discovers survey images using the CASDA SIA 1 interface, which is clear but does not differentiate from the sibling casda_search_images, which might serve a similar purpose.

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 is provided on when to use this tool versus alternatives like casda_search_images or casda_list_image_surveys. The description lacks any contextual use cases or exclusions.

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