Skip to main content
Glama
Sign In
oddsky

oddsky

by AlanShortz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

list_cases

Retrieve available investigation cases and their discovery-ladder status so you can identify which real-time astronomy targets to examine next.

Instructions

List the cases you can investigate, with their status on the discovery ladder.

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": "list_cases"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

B3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. 'Discovery ladder' is never explained -- an agent cannot tell what statuses exist, whether the list is ordered or paginated, or whether it is filtered to the caller's own cases, which is the main behavioural question for a tool with no parameters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no wasted words. It is efficient, though the unexplained 'discovery ladder' phrase costs it a point since a short gloss would have made the sentence fully informative.

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?

With no annotations, no output schema, and no parameters, the description is the only source of behavioural information, yet it omits the return shape, the meaning of the ladder statuses, and any scoping or ordering rules. For a zero-arg enumeration tool the agent is left guessing what it will actually receive.

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 tool takes zero parameters, so there is nothing for the description to clarify beyond the input schema; baseline 4 applies.

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?

States a specific verb and resource: 'List the cases you can investigate'. That is clear enough to distinguish it from action siblings like open_case or case_overview, but it draws no explicit contrast with the nearby list_classes and never defines what a 'case' or a 'discovery ladder' is.

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 phrase 'the cases you can investigate' hints that this is an entry-point enumeration tool, but there is no explicit when-to-use guidance, no statement of when to prefer case_overview or list_classes, and no note about prerequisites such as needing an authenticated observer.

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