Skip to main content
Glama

Change a price alert

edit_price_alert
DestructiveIdempotent

Changes a price alert's threshold or note, or re-arms one that fired so it watches again, as the alerts list on the page does. A new threshold or a re-arm counts only prices after it. The stop and target alerts that follow a holding's plan can be re-armed; their level changes with set_stop_target. 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": "edit_price_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe alert id, from get_price_alerts or create_price_alert.
noteNoThe new note; null or "" clears it.
rearmNotrue: a fired alert watches again.
thresholdNoThe new price.
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
done_atNo
warningsNo
unchangedNo
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.6/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, and the description adds real context on top: the preview/confirm gate ('sent without preview_id, it changes nothing'), and that a new threshold or re-arm only counts prices after it. It stops short of saying what is actually destroyed or whether the prior alert state is recoverable, which matters for a destructive-flagged 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?

Purpose is front-loaded and each sentence adds a distinct rule (scope, retroactivity, re-arm exception, preview flow). Some sentences are long multi-clause run-ons and the 'as the alerts list on the page does' comparison is mildly opaque, but there is no filler.

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 destructive mutation with five parameters, an output schema, and full annotations, the description covers the missing pieces an agent needs: the preview handshake, forward-only semantics of threshold/rearm, and the sibling that handles plan-driven level changes. Nothing required to call it correctly is absent.

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 the baseline is 3, but the description earns extra: it explains that preview_id is a two-phase confirmation token bound to the same arguments, and that threshold/rearm are forward-looking rather than retroactive. That adds meaning the schema's per-parameter text does not carry.

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?

States a specific verb and resource ('Changes a price alert's threshold or note, or re-arms one that fired') and enumerates the exact mutable fields. It also explicitly separates itself from set_stop_target for plan-driven stop/target alerts, so an agent can route correctly without opening another 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 explicit when-to-use (change threshold/note, re-arm a fired alert) and when-to-use-something-else (level changes on stop/target alerts go through set_stop_target). It also spells out the mandatory two-call preview pattern, so an agent knows the exact invocation sequence rather than inferring it.

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.