Skip to main content
Glama
Sign In
CASDA MCP Server

CASDA MCP Server

by jbwod
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Search CASDA catalogue

casda_search_catalogue
Read-onlyIdempotent

Search a CASDA catalogue by position and radius. Provide a catalogue short name, right ascension, declination, and search radius in degrees to return matching records.

Instructions

Run a Simple Cone Search against one CASDA catalogue short-name endpoint.

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": {
      "catalogue": "<catalogue>",
      "ra_deg": "<ra_deg>",
      "dec_deg": "<dec_deg>",
      "radius_deg": "<radius_deg>"
    },
    "name": "casda_search_catalogue"
  }
}

Input Schema

NameRequiredDescriptionDefault
ra_degYesICRS right ascension in degrees, in [0, 360).
dec_degYesICRS declination in degrees, in [-90, 90].
catalogueYesSCS catalogue short name matching ^[A-Za-z][A-Za-z0-9._-]{0,63}$, such as racs_mid_sources_v01.
radius_degYesCone search radius in degrees; server-bounded.
max_recordsNoMaximum rows to return; bounded by server configuration.

Output Schema

NameRequiredDescriptionDefault
rowsNo
errorNo
returnedYes
catalogueYes
provenanceNo
max_recordsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already indicate readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, which fully disclose the safety profile. The description adds minimal behavioral context by naming the query type, but no further traits like result limits or authentication needs are mentioned.

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 sentence, which is concise, but it is vague and lacks detail. It could be more informative without increasing length significantly.

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?

Given the tool's complexity (astronomical cone search) and the large number of sibling tools, the description fails to provide sufficient context for an AI agent to understand the tool's purpose or usage. An output schema exists, so return values are covered, but the core functionality is under-explained.

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%, so parameters are already well-documented. The description adds no extra meaning beyond the schema, which is acceptable but not helpful. Baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool performs a 'Simple Cone Search' against a CASDA catalogue, which is a specific astronomical query. However, it does not differentiate from sibling search tools like casda_search_images or casda_search_spectra, and the term 'Simple Cone Search' may be unclear to non-experts.

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?

The description gives no guidance on when to use this tool instead of alternatives, such as casda_search_products or casda_search_images. No context about prerequisites or exclusions is 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