Skip to main content
Glama

Cancel an alert creation

cancel_alert_creation
DestructiveIdempotent

Cancel an unapproved creation. Does not delete an alert already created.

Permission: monitoring:manage.

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": {
      "creation_id": "<creation_id>"
    },
    "name": "cancel_alert_creation"
  }
}

Input Schema

NameRequiredDescriptionDefault
creation_idYesThe creation ID returned when it was quoted or created.

Output Schema

NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds two things the annotations cannot: the required permission scope (monitoring:manage) and the semantic boundary that only pre-approval creations are destroyed while live alerts are untouched, which is exactly the context needed before an irreversible call.

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?

Three short sentences with zero filler: the action first, the exclusion second, the prerequisite permission last. Nothing is restated from the name or annotations.

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 single-parameter cancel operation with an output schema and strong annotation coverage, the description supplies the permission requirement and the destructive-scope boundary. The only meaningful gap is that it does not say what a cancelled creation returns or whether the call fails on an already-approved creation.

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?

Only one parameter, and the schema already documents it at 100% coverage including the UUID format and the note that the ID comes from the quote/create step. The description adds no further syntax, sourcing, or error-condition meaning beyond the schema, so the 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?

States a specific verb (cancel) and a specific resource with scope (an unapproved creation), and the second sentence rules out the adjacent operation of deleting an already-created alert. It does not name the nearby sibling cancel_alert_update, so an agent must infer the creation-vs-update distinction from the noun alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear when-to-use condition (creation not yet approved) and an explicit when-not (alert already created — this will not delete it). What is missing is any pointer to the tool to use instead for an already-created alert, or to cancel_alert_update for the update-object case.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources