Skip to main content
Glama

Cancel a price alert

cancel_price_alert
Idempotent

Remove a waiting price alert so it never fires. Use when the user no longer wants it or to make room (at most 20 wait). Not for orders (use cancel_order). Input: alert_id from get_my_price_alerts. An app can delete only the alerts it created. Next: get_my_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": {
      "alert_id": "<alert_id>"
    },
    "name": "cancel_price_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
alert_idYesFrom set_price_alert or get_my_price_alerts

Output Schema

NameRequiredDescriptionDefault
priceYesThe level, USD per coin
venueYesThe exchange whose mark is watched; null: the reference price (median of the exchanges' marks; on the sandbox deployment the sandbox's real-market price)
statusYesactive (waiting), triggered (fired once, done) or deleted
symbolYesBase coin
alert_idYesAlert id, alr_…
directionYesabove: fires when the price is at or above the level; below: at or below
created_atYesISO 8601 UTC
created_byYesThe agent that created it, or person
deprecationNoPresent only while this tool is deprecated: replacement, removal_date, changelog
triggered_atNoWhen it fired, ISO 8601 UTC
current_priceNoOn creation: the price it is compared with now, USD per coin
triggered_priceNoThe price that fired it, USD per coin

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed30 schema fields changed
    • removedInput schema / properties / alert_id / title
      Removed value: -"Alert Id"
    • removedInput schema / title
      Removed value: -"cancel_price_alertArguments"
    • removedOutput schema / properties / alert_id / title
      Removed value: -"Alert Id"
    • removedOutput schema / properties / created_at / title
      Removed value: -"Created At"
    • removedOutput schema / properties / created_by / title
      Removed value: -"Created By"
    • removedOutput schema / properties / current_price / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • removedOutput schema / properties / current_price / default
      Removed value: -null
    • removedOutput schema / properties / current_price / title
      Removed value: -"Current Price"
    • addedOutput schema / properties / current_price / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • addedOutput schema / properties / deprecation / additionalProperties
      Added value: +true
    • removedOutput schema / properties / deprecation / anyOf
      Removed value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • removedOutput schema / properties / deprecation / default
      Removed value: -null
    • removedOutput schema / properties / deprecation / title
      Removed value: -"Deprecation"
    • addedOutput schema / properties / deprecation / type
      Added value: +[
      +  "object",
      +  "null"
      +]
    • removedOutput schema / properties / direction / title
      Removed value: -"Direction"
    • removedOutput schema / properties / price / title
      Removed value: -"Price"
    • removedOutput schema / properties / status / title
      Removed value: -"Status"
    • removedOutput schema / properties / symbol / title
      Removed value: -"Symbol"
    • removedOutput schema / properties / triggered_at / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • removedOutput schema / properties / triggered_at / default
      Removed value: -null
    • removedOutput schema / properties / triggered_at / title
      Removed value: -"Triggered At"
    • addedOutput schema / properties / triggered_at / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / triggered_price / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • removedOutput schema / properties / triggered_price / default
      Removed value: -null
    • removedOutput schema / properties / triggered_price / title
      Removed value: -"Triggered Price"
    • addedOutput schema / properties / triggered_price / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / venue / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • removedOutput schema / properties / venue / title
      Removed value: -"Venue"
    • addedOutput schema / properties / venue / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / title
      Removed value: -"PriceAlert"
  2. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, so the safety profile is covered; the description adds value beyond that with the capacity constraint (at most 20 waiting) and the ownership rule that an app can delete only alerts it created — real permission context. It stops short of stating what happens when the alert has already fired or does not exist, which is the main remaining behavioral gap.

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?

Front-loaded with the action and effect, then usage, exclusion, input provenance, constraint, and next step — each fragment earns its place with no filler. The telegraphic style is dense but readable.

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?

For a single-parameter mutation with an output schema and full annotation coverage, nothing an agent needs is missing: what it does, when to use it, what not to confuse it with, where the ID comes from, and the ownership limit. Return values need not be explained because an output schema exists.

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 schema already says the id comes from set_price_alert or get_my_price_alerts, so the description's "Input: alert_id from get_my_price_alerts" is largely redundant. Baseline 3 is appropriate since the schema carries the semantics.

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?

Specific verb and resource with scope: "Remove a waiting price alert so it never fires" — the 'waiting' qualifier distinguishes it from cancelling an order or closing a position. It also names the sibling it is not (cancel_order), so an agent can route correctly without opening a schema.

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?

Gives both when-to-use (user no longer wants it, or to make room under the 20-alert cap) and an explicit exclusion with the alternative ("Not for orders (use cancel_order)"). It also supplies a follow-up action, which is more than most definitions attempt.

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