Skip to main content
Glama

Delete a price alert

delete_price_alert
DestructiveIdempotent

Deletes a price alert, as the alerts list on the page does. The signals it fired stay. The stop and target alerts that follow a holding's plan are refused: clearing the level with set_stop_target removes them. Sent without preview_id, it changes nothing and returns a preview of the change with a preview_id; sent again with the same arguments and that preview_id, it makes the change.

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
idYesThe alert id, from get_price_alerts or create_price_alert.
preview_idNoThe preview_id that the same call without it returned. Without it, nothing is changed.

Output Schema

NameRequiredDescriptionDefault
noteNo
toolNo
alertNo
errorNo
tradeNo
changeNo
statusNo
deletedNo
done_atNo
warningsNo
preview_idNo
confirm_on_cardNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / confirm_on_card
      Added value: +{
      +  "type": "boolean"
      +}
  2. Changed2 schema fields changed
    • addedOutput schema / properties / error / properties / reason
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / warnings
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  3. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, but the description adds material context beyond them: the exact side-effect boundary (fired signals remain), the refusal behavior for plan-linked stop/target alerts, and a preview-then-commit protocol where a call without preview_id changes nothing. That is precisely the operational detail an agent needs before invoking a 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.

Conciseness4/5

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

Four short sentences, front-loaded with the action and its scope, then the exception, then the preview protocol — no filler. The phrasing is somewhat telegraphic ('as the alerts list on the page does', 'The signals it fired stay'), which is efficient but requires a second read in places.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation. Given a destructive mutation with a two-phase confirmation and an exception path, the description covers everything required to call it correctly: what is deleted, what persists, when it is refused, and how to actually commit the change.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both parameters are already documented and the baseline is 3. The description nonetheless adds operational meaning to preview_id by explaining the confirm sequence ('sent again with the same arguments and that preview_id, it makes the change'), and it clarifies that id is sourced from get_price_alerts or create_price_alert — a modest but real increment over the schema text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ('Deletes a price alert') and immediately bounds the scope by stating the UI-equivalent behavior ('as the alerts list on the page does') plus what survives ('The signals it fired stay'). It also carves out a distinct case it does not handle (stop/target alerts tied to a holding's plan), so an agent can tell it apart from set_stop_target.

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

Usage Guidelines5/5

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

Explicit when-not guidance: stop and target alerts that follow a holding's plan are refused, and the description names set_stop_target as the alternative that clears the level instead. It also spells out the two-step invocation pattern (call without preview_id, then repeat with it), which is the practical condition for actually performing the delete.

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.