Skip to main content
Glama

Delete an escalation policy

delete_escalation_policy
DestructiveIdempotent

Deletes a policy; its monitors go back to alerting their own contacts. Free.

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": {
      "policy_id": "<policy_id>"
    },
    "name": "delete_escalation_policy"
  }
}

Input Schema

NameRequiredDescriptionDefault
policy_idYesPolicy ID from list_escalation_policies.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, so the safety profile is known. The description adds genuinely new behavior beyond that: monitors attached to the policy revert to alerting their own contacts, which is exactly the consequence an agent needs before calling a destructive tool. It omits irreversibility and what happens to in-flight alerts, keeping it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The two-clause structure is front-loaded and efficient, but the trailing word "Free" is cryptic — it implies a billing or plan implication without saying what is free (the deletion, the resulting monitors, the plan tier). A fragment that raises a question rather than answering one does not earn its place.

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 destructive tool with full annotation coverage and no output schema, the definition covers the key side effect, so an agent can act. It leaves notable gaps: whether deletion is recoverable, what happens to currently open incidents routed through the policy, and what "Free" actually means.

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 a single parameter at 100% schema description coverage, the schema already explains policy_id and even points to list_escalation_policies as the source. The description adds nothing about the parameter, 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 and resource ("Deletes a policy"), which is clearly distinguishable from the create_/update_escalation_policy siblings and from delete_monitor/delete_on_call_schedule by the named resource. It stops short of an explicit sibling comparison, but the action is unambiguous.

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 when-to-use or when-not-to-use guidance is given, and no prerequisites or alternatives are named. The only hint about consequences is the side effect sentence, which does not tell an agent when deletion is preferable to updating or reassigning the policy.

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