Skip to main content
Glama

delete_cluster_report

Deletes a specified cluster report and its intermediate summaries by report ID.

Instructions

Delete a cluster report and its intermediate summaries.

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

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 behavioral burden. It usefully discloses that intermediate summaries are also removed, but omits whether deletion is irreversible, what permissions are required, whether the operation is idempotent, and how missing or invalid IDs are handled. For a destructive operation this leaves major gaps.

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; it states the action and collateral deletion immediately. Nothing can be removed without losing meaning.

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, no-output-schema deletion tool, the description covers the core effect and collateral deletion. However, because there are no annotations to declare destructiveness, permissions, or reversibility, it is not fully complete for safe invocation.

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 single 'id' parameter is already documented as the Cluster Report ID to delete. The description adds no further parameter meaning such as format, range, or how to obtain the ID, so baseline 3 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?

The description gives a specific verb and resource ('Delete a cluster report') plus the collateral effect ('and its intermediate summaries'), separating it from deletion of snapshots or other resources. It does not explicitly contrast with sibling delete tools, so it falls short of the highest sibling-routing clarity.

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?

No indication is given for when this tool should be used instead of alternatives, what preconditions must hold, or what to do if the report is referenced elsewhere. Usage is only implied by the verb 'Delete'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.