Skip to main content
Glama
Sign In
Astronomer MCP Server

Astronomer MCP Server

by leouofa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_report_summaries

Lists all Phase 1 per-cluster analyses for a synthesis report by cluster_report_id, letting users inspect which cluster summaries are included.

Instructions

List all Phase 1 per-cluster analyses belonging to a synthesis report.

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": {
      "cluster_report_id": "<cluster_report_id>"
    },
    "name": "list_report_summaries"
  }
}

Input Schema

NameRequiredDescriptionDefault
cluster_report_idYesCluster Report ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/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. It discloses the scope filter, but says nothing about ordering, pagination, permissions, or what is returned for a report with no analyses.

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 front-loaded sentence with no filler. Every word contributes to stating the resource and the relationship being traversed.

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?

For a one-parameter read tool without an output schema or annotations, the description covers the basic purpose but omits return format and pagination behavior. It is minimally adequate but leaves meaningful gaps for an agent invoking it.

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 schema already documents cluster_report_id. The description adds some meaning by stating that the listed items are Phase 1 per-cluster analyses belonging to a synthesis report, but it does not clarify why the required parameter is a cluster_report_id rather than a synthesis report identifier.

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 uses a specific verb and resource: 'List all Phase 1 per-cluster analyses belonging to a synthesis report.' That clearly identifies the operation and the type of items returned, though the phrase 'synthesis report' is slightly at odds with the parameter name cluster_report_id and no sibling alternative is named.

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?

There is no explicit guidance on when to use this tool versus siblings such as list_report_sub_reports or get_report_summary. The only implied usage is that the caller must already have a cluster report and wants its associated Phase 1 analyses.

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