Skip to main content
Glama
Sign In
Astronomer MCP Server

Astronomer MCP Server

by leouofa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

delete_cluster_report

Delete a cluster synthesis report and all related intermediate summaries and sub-reports by its ID to clean up outdated astrophysics research data.

Instructions

Delete a synthesis report along with its intermediate summaries and sub-reports.

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

Input Schema

NameRequiredDescriptionDefault
idYesCluster Report ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses cascade deletion of intermediate summaries and sub-reports, but omits irreversibility, permission requirements, and failure or atomicity behavior.

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?

It is a single front-loaded sentence with the verb, resource, and destructive scope stated immediately. There is no filler or ambiguous structure.

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 one-parameter destructive tool with no output schema, the description identifies the key cascade effect an agent must know before calling it. It remains thin on safety and permission context, but is adequate for the tool's low complexity.

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%, and the sole id parameter is documented in the schema as the Cluster Report ID to delete. The description adds no format, constraint, or lookup guidance beyond what the schema already provides.

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?

The description states a specific verb, "Delete," and a specific resource, "synthesis report," plus the cascade scope involving intermediate summaries and sub-reports. This lets an agent distinguish it from create/get/list report siblings and from delete_cluster_snapshot by the named resource.

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?

It gives no when-to-use, when-not-to-use, prerequisite, or alternative guidance. There is no mention of delete_cluster_snapshot, confirmation requirements, or conditions under which deleting a report is 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