Skip to main content
Glama

Airsockfly

Delete price alert

delete_price_alert
DestructiveIdempotent

Delete one of the user's price alerts.

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_price_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesAlert identifier from list_price_alerts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/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 agent knows this is a permanent mutation. The description adds no further behavioral context — nothing about irreversibility, confirmation, or what happens to an alert that has already fired — but with full annotation coverage that gap is acceptable rather than critical.

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 short sentence with zero filler, and the destructive action is front-loaded in the verb. Nothing could 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 delete behind rich annotations this is close to sufficient, but it omits anything about irreversibility or what a successful call returns (there is no output schema). A brief note that the alert is permanently removed and cannot be restored would close the remaining gap.

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 description coverage is 100%, and the schema itself documents the single parameter with both a regex pattern and a pointer to list_price_alerts as the id source. The description adds no meaning beyond that, which is the baseline expectation when the schema does the heavy lifting.

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 states a specific verb and resource ('Delete ... price alerts') and scopes it to the user's own alerts, so an agent knows exactly what the tool does. It does not, however, distinguish itself from siblings like create_price_alert or cancel_booking beyond the obvious verb difference.

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

Usage Guidelines3/5

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

Usage is only implied: the phrase 'one of the user's price alerts' suggests an existing alert is required, and the schema's note that the id comes 'from list_price_alerts' hints at the prerequisite flow. There is no explicit when-to-use, when-not-to-use, or named alternative in the description itself.

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