Skip to main content
Glama
Sign In
Astronomer MCP Server

Astronomer MCP Server

by leouofa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_report_summary

Retrieve a single Phase 1 per-cluster scholarly summary by its report summary ID for targeted astrophysics review.

Instructions

Retrieve a single Phase 1 per-cluster scholarly summary.

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": {
      "id": "<id>"
    },
    "name": "get_report_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCluster Report Summary ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations exist, so the description carries the full burden of disclosure. 'Retrieve a single' weakly implies a read-only, one-record lookup, but nothing is said about behavior when the ID does not exist, whether the report must be finalized, access requirements, or the shape/size of the returned summary.

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 filler or redundancy. It is efficient, though its brevity comes at the cost of the missing detail noted in other dimensions.

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 low-complexity one-parameter read tool with a fully documented schema and no output schema, the description covers the minimum needed to attempt a call. It still leaves 'Phase 1' and what the summary contains undefined, which matters for deciding whether this is the right retrieval tool.

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 one required parameter at 100% schema description coverage, the schema already explains 'Cluster Report Summary ID' including its positive-integer constraint. The description adds no further meaning about which ID namespace or entity this refers to, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'Retrieve' and the object 'a single ... summary' are stated, so the basic operation is identifiable. But 'Phase 1 per-cluster scholarly summary' is domain jargon that the description never unpacks, and it gives no way to tell this apart from siblings like get_cluster_report or get_report_sub_report, which read as plausibly overlapping.

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 guidance on when to use this versus get_cluster_report, list_cluster_reports, or get_report_sub_report. The only implied cue is 'single' versus list-style siblings, which the agent must infer on its own.

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