Skip to main content
Glama
Sign In
CASDA MCP Server

CASDA MCP Server

by jbwod
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Submit CASDA async TAP query

casda_submit_tap_query

Submit a SELECT-only ADQL query to create and start an asynchronous TAP job for searching the CASDA archive.

Instructions

Create and start one async TAP job for validated SELECT-only ADQL.

Requires CASDA_ENABLE_ADVANCED_ADQL. Create and RUN are never automatically retried.

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": {
      "query": "<query>"
    },
    "name": "casda_submit_tap_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSELECT-only ADQL submitted as an async TAP/UWS job.

Output Schema

NameRequiredDescriptionDefault
errorNo
statusYes
provenanceNo
request_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations give readOnlyHint=false and destructiveHint=false, but the description adds that 'Create and RUN are never automatically retried', which is not covered by annotations. It also implies the tool expects pre-validated ADQL, adding behavioral context beyond structured fields.

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 sentences: first states the function, second gives requirements and retry behavior. No wasted words, front-loaded with the core purpose. Excellent conciseness.

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

Completeness4/5

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

Given a single parameter and existence of output schema, the description covers the main purpose, a precondition, and retry policy. It omits error handling or chaining with result retrieval tools, but for a submission tool, it is largely complete.

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 schema already describes the query parameter as 'SELECT-only ADQL submitted as an async TAP/UWS job.' The tool description adds 'validated' and the precondition, but these are marginal additions. Baseline 3 is appropriate as the description adds limited value beyond 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 'Create and start one async TAP job for validated SELECT-only ADQL', specifying the verb (create, start), resource (async TAP job), and constraint (SELECT-only ADQL). This differentiates it from siblings like casda_tap_query (likely sync) and casda_validate_adql (only validation).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description mentions a precondition ('Requires CASDA_ENABLE_ADVANCED_ADQL') and a behavioral note ('Create and RUN are never automatically retried'), providing context for when to use the tool. It does not explicitly compare to alternatives, but the async nature and SELECT-only restriction imply usage situations.

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