Skip to main content
Glama
Sign In
Astronomer MCP Server

Astronomer MCP Server

by leouofa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

delete_cluster_snapshot

Delete a frozen cluster snapshot and its cascaded cluster groups and synthesis reports by ID.

Instructions

Delete a frozen cluster snapshot along with its cascaded cluster groups and synthesis 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_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCluster Snapshot ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden and does disclose one important trait: the delete cascades to cluster groups and synthesis reports. It does not state irreversibility, whether confirmation or elevated permissions are required, or what happens to snapshots referenced by running jobs – significant gaps for an unannotated destructive tool.

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?

A single front-loaded sentence with no filler; the destructive verb comes first and the cascade consequence follows immediately.

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 destructive, unannotated tool with no output schema, the description covers the action and the cascade side effects but omits reversibility, authorization, and failure behavior. It is adequate to identify the tool but thin for the risk profile.

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% for the single 'id' parameter, so the schema already defines it as the positive Cluster Snapshot ID to delete. The description adds no syntax, format, or lookup guidance beyond that, matching the baseline for high-coverage schemas.

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 ('Delete') and resource ('frozen cluster snapshot') and adds scope detail by naming what is removed with it: cascaded cluster groups and synthesis reports. An agent can distinguish this from create_cluster_snapshot and get_cluster_snapshot by the verb alone, though no sibling is named explicitly.

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 when-to-use or when-not-to-use guidance, no mention of prerequisites such as confirming the snapshot is not the base for pending jobs, and no pointer to alternatives. The cascade clause implies this is the destructive path but never says so as guidance.

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