Skip to main content
Glama
jbwod

CASDA MCP Server

by jbwod

Build CASDA ADQL

casda_build_adql
Read-onlyIdempotent

Construct an ADQL query string for searching ObsCore observations and products using specified filters, without contacting the CASDA server.

Instructions

Build the allowlisted ObsCore search ADQL string without contacting CASDA.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoOne-based page within the configured bounded result window.
ra_degNoICRS right ascension in degrees, in [0, 360).
dec_degNoICRS declination in degrees, in [-90, 90].
sort_byNoAllowlisted sort field: product_id, filename, file_size, observation_start, release_date, distance.product_id
page_sizeNoNumber of results to return; bounded by server configuration.
collectionNoExact ObsCore collection name.
radius_degNoCone radius in degrees; bounded by server configuration.
sort_orderNoSort direction: asc or desc.asc
source_nameNoExact CASDA target name; this tool does not resolve names.
project_codeNoExact OPAL/CASDA project code, such as AS102.
facility_nameNoExact ObsCore facility_name filter.
product_typesNoAllowlisted types: image, cube, visibility, spectrum, catalogue, weight, moment_map, cubelet, evaluation, scan.
released_onlyNoWhen true, require a non-null obs_release_date in the ADQL.
instrument_nameNoExact ObsCore instrument_name filter.
observation_endNoLatest overlapping observation date/time in ISO 8601.
frequency_max_hzNoUpper overlapping spectral frequency in hertz.
frequency_min_hzNoLower overlapping spectral frequency in hertz.
observation_startNoEarliest overlapping observation date/time in ISO 8601.
scheduling_block_idNoPositive ASKAP scheduling block identifier.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNo
queryYes
parametersNo
provenanceNo
max_recordsYes
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds 'without contacting CASDA', confirming local operation. This is useful but does not disclose additional behavioral traits beyond what annotations provide.

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?

The description is a single concise sentence, front-loaded with the core purpose, containing no redundant or extraneous words.

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

Completeness3/5

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

Given the tool has 19 parameters, full schema documentation, and an output schema, the description is adequate but minimal. It does not explain what the ADQL string represents or how parameters are combined, but the output schema likely covers the return format.

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?

With 100% schema description coverage, the baseline is 3. The description adds no parameter-specific information beyond what is already in 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 tool builds an ADQL string locally ('without contacting CASDA'), specifying the verb 'Build' and the resource 'allowlisted ObsCore search ADQL string'. This distinguishes it from sibling tools like casda_tap_query which execute queries.

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 use for offline ADQL construction but does not explicitly state when to use this tool over alternatives like casda_validate_adql or casda_tap_query. No when-not or prerequisite guidance is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jbwod/CASDA-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server