Skip to main content
Glama

price_alert

Read-onlyIdempotent

Webhook when a Base token crosses your target — Pay once to register a price-threshold alert on any Base token. Supply target price, direction (above/below), and an https webhook URL. A cron checks DexScreener every 30 minutes and POSTs your webhook when it crosses — HMAC-signed (secret returned once at registration), retried up to 3 times. Expires after 30 days. Or omit the webhook and poll with check=: the verdict is THRESHOLD_MET, ok, FIRED, or unknown when the price feed could not be read. Required inputs: token, threshold, direction. Priced $0.05 per call over x402 on Base; send a prepaid x-credit-token header for unlimited calls, or get 1 free call/day per tool. No API key required.

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": {
      "token": "<token>",
      "threshold": "<threshold>",
      "direction": "<direction>"
    },
    "name": "price_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
checkNoOr: alert id to poll its status
tokenYesToken address
webhookNoWebhook URL (optional — omit to poll)
directionYesDirection (above/below)
thresholdYesPrice threshold (USD)

Output Schema

NameRequiredDescriptionDefault
dataNoThe result payload. Shape is service-specific; every field is documented in the tool description.
serviceNoThe service id that answered.
checkedAtNoISO-8601 timestamp of when the underlying reads were taken.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / data / description
      Previous value: -"The result payload. Shape is service-specific; every field is documented in the service description above."New value: +"The result payload. Shape is service-specific; every field is documented in the tool description."
  2. Changed1 schema field changed
    • removedOutput schema / required
      Removed value: -[
      -  "data"
      -]
  3. Added

TDQS

A4.1/5.0
Behavior2/5

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

In isolation the description is unusually transparent: 30-minute cron polling of DexScreener, HMAC-signed POSTs with a secret returned once, 3 retries, 30-day expiry, and named poll verdicts. However, it describes a paid registration that persists server-side state, which contradicts the supplied readOnlyHint=true and casts doubt on idempotentHint=true; that inconsistency is exactly the kind of behavioral trait annotations should settle, and here they conflict.

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?

The primary action and its required inputs are front-loaded, and every clause carries operational information (cost, expiry, retries, polling fallback). It runs long as a single block, and the verdict enumeration partly duplicates the output schema, so a small amount could be trimmed.

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

Completeness4/5

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

For a paid, scheduled-webhook tool the description covers cost and payment headers, free-tier limits, no-API-key auth, delivery guarantees, expiry, and the polling alternative — far beyond what annotations or schema convey. It stops short of stating that a registration returns an alert id needed for check=<id>, which it only implies.

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 more: it explains that webhook must be https and that the HMAC secret is returned only once at registration, and it documents the check=<id> polling path and the four possible verdicts. Threshold units (USD) and direction (above/below) merely repeat the schema, which caps it below 5.

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?

The description states a specific verb and resource — register a price-threshold alert on a Base token, with an https webhook — and explicitly separates that mode from the polling mode (check=<id>). An agent can tell this apart from a plain price lookup such as token_price without opening the 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?

It gives explicit when-to-use guidance (supply token, threshold, direction, webhook) and an explicit when-not/alternative (omit the webhook and poll with check=<id>), plus the consequence of each choice. Required inputs are restated so selection and invocation are unambiguous.

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