Skip to main content
Glama
Sign In
CASDA MCP Server

CASDA MCP Server

by jbwod
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

List CASDA catalogues

casda_list_catalogues
Read-onlyIdempotent

Retrieve catalogue product rows from the ASKAP archive with stable cursor pagination for controlled, auditable data access.

Instructions

List casda.catalogue product rows with stable cursor pagination.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "casda_list_catalogues"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoOpaque next-page cursor from a previous catalogue inventory.
page_sizeNoNumber of catalogue products to return; server-bounded.

Output Schema

NameRequiredDescriptionDefault
errorNo
cataloguesNo
paginationNo
provenanceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

The description adds 'stable cursor pagination' which provides behavioral context beyond the annotations (readOnlyHint, openWorldHint, idempotentHint, destructiveHint). This indicates that pagination results remain consistent across requests.

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 sentence, no waste. Front-loaded with the action and resource.

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

Completeness5/5

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

Given the output schema exists and annotations cover behavior, the description is complete. It highlights the key pagination feature and does not leave significant gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema covers both parameters with descriptions (100% coverage), so baseline is 3. The description adds context about cursor stability, which enhances understanding of the cursor parameter. However, it doesn't add new info about page_size.

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 clearly states it lists catalogue product rows with stable cursor pagination. The verb 'List' and resource are specific, but it doesn't explicitly differentiate from casda_search_catalogue which also deals with catalogues.

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 use this tool vs alternatives like casda_search_catalogue. The description only states what it does, not when it's appropriate.

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