Skip to main content
Glama
Sign In
CASDA MCP Server

CASDA MCP Server

by jbwod
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Abort CASDA data job

casda_abort_data_job

Abort a previously created SODA/UWS data job by providing its request ID to halt processing and release resources.

Instructions

Abort a SODA/UWS data job previously created by this server.

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": {
      "request_id": "<request_id>"
    },
    "name": "casda_abort_data_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idYesData job identifier returned by this server.

Output Schema

NameRequiredDescriptionDefault
errorNo
statusYes
provenanceNo
request_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations provide basic flags but description adds no extra behavioral context (e.g., reversibility, side effects). It is neutral and not contradictory.

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?

Single succinct sentence, no redundancy, front-loaded with the key action.

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?

For a simple abort with one parameter and output schema, the description is adequate. No critical gaps, but could hint at what aborting entails.

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 the description adds minimal value beyond stating 'Data job identifier returned by this server.' No parameter details enhanced.

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?

Clearly states the action (abort) and the resource (SODA/UWS data job). It is specific and distinguishes from other operations like creation or deletion.

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 abort vs. delete, or any prerequisites. Siblings like casda_delete_data_job exist but no differentiation 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