agent-embassy

Compute Alerts

compute_alerts

Idempotent

Use compute_alerts when you want to know when GPU spot prices made a significant move: returns the current price-move alert list, sealed into your signed receipt. POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header. See https://docs.cdp.coinbase.com/x402 Paid tool — $0.25, USDC on Base or Arbitrum One. Paid URL: https://aemb.pro/v1/markets/compute/alerts.

Input Schema

TableJSON Schema

Name	Required	Description
`gpu`	No	Optional GPU filter, e.g. 'H100 SXM' (max 64 chars). Omit for all GPUs
`limit`	No	Max alerts to return; integer 1-50. Defaults to 25
`idempotency_key`	Yes	Idempotency key: UUID v4, client-generated, one per logical request. Replaying the same key on this tool returns the original receipt — the action is not re-run, and the first request's receipt wins even if you resend different inputs. Published example keys are rejected. Keys are scoped per tool and per payer account: a key never returns another wallet's receipt.

Output Schema

TableJSON Schema

Name	Required	Description
`how`	Yes	How to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header
`tool`	Yes	Tool name, e.g. verified_check
`asset`	Yes	Settlement asset
`price`	Yes	Exact price, e.g. "$0.15"
`networks`	Yes	EVM CAIP-2 network ids accepted
`paid_url`	Yes	x402-paid HTTPS URL to POST the tool inputs to
`facilitator`	Yes	x402 facilitator
`payment_required`	Yes	Always true: this MCP tool is a payment pointer; the tool itself is monetized via x402.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 26, 2026

removedInput schema / properties / agent_wallet

Removed value: -{
-  "description": "Dev mode only: declares the account wallet (string, min 20 chars) when no x402 payment is present. Ignored in live mode — there the wallet is recovered from the verified payment authorization.",
-  "type": "string"
-}

changedInput schema / properties / idempotency_key / description

Previous value: -"Idempotency key: any non-empty string (a UUID is recommended; no format is enforced). Replaying the same key on this tool returns the original receipt — the action is not re-run, and the first request's receipt wins even if you resend different inputs. Keys are scoped per tool: the same key on another tool is unrelated."New value: +"Idempotency key: UUID v4, client-generated, one per logical request. Replaying the same key on this tool returns the original receipt — the action is not re-run, and the first request's receipt wins even if you resend different inputs. Published example keys are rejected. Keys are scoped per tool and per payer account: a key never returns another wallet's receipt."

Changed4 schema fields changedSep 24, 2026

changedInput schema / properties / agent_wallet / description

Previous value: -"dev mode only"New value: +"Dev mode only: declares the account wallet (string, min 20 chars) when no x402 payment is present. Ignored in live mode — there the wallet is recovered from the verified payment authorization."

addedInput schema / properties / gpu / description

Added value: +"Optional GPU filter, e.g. 'H100 SXM' (max 64 chars). Omit for all GPUs"

addedInput schema / properties / idempotency_key / description

Added value: +"Idempotency key: any non-empty string (a UUID is recommended; no format is enforced). Replaying the same key on this tool returns the original receipt — the action is not re-run, and the first request's receipt wins even if you resend different inputs. Keys are scoped per tool: the same key on another tool is unrelated."

addedInput schema / properties / limit / description

Added value: +"Max alerts to return; integer 1-50. Defaults to 25"

Changed4 schema fields changedSep 22, 2026

changedInput schema / properties / agent_wallet / description

Previous value: -"DEV MODE ONLY: wallet to attribute. In live mode the payer wallet from the verified x402 payment is used."New value: +"dev mode only"

removedInput schema / properties / gpu / description

Removed value: -"Class, e.g. 'H100 SXM'. Omit for all classes."

removedInput schema / properties / idempotency_key / description

Removed value: -"Client-generated UUID; retries return the original receipt"

removedInput schema / properties / limit / description

Removed value: -"Max alerts returned, 1-50 (default 25, most recent first)."

Changed1 schema field changedSep 21, 2026

changedInput schema / properties / gpu / description

Previous value: -"GPU class, e.g. 'H100 SXM'. Omit for all classes."New value: +"Class, e.g. 'H100 SXM'. Omit for all classes."

AddedSep 21, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations, the description discloses the paid nature ($0.25), payment network, required x402 v2 PAYMENT-SIGNATURE auth, the fact that results are sealed into a signed receipt, and the actual paid URL. This is significant behavioral context an agent needs before invoking a paid tool.

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?

The description is compact and front-loaded: the use case and return value come first, followed by auth/payment/URL details. Every sentence contributes operational value; there is no filler or repetition.

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?

With an output schema present and the schema covering all parameters, the only missing operational context was payment/auth and endpoint details, all of which are provided. A link to the x402 docs fills the remaining procedural 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?

All three parameters are already documented with 100% schema coverage, including the idempotency-key semantics, so the description carries no additional parameter meaning. Baseline 3 is appropriate because the schema does the heavy lifting and the description need not repeat it.

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 names a concrete operation ('returns the current price-move alert list') and pins the domain precisely ('when GPU spot prices made a significant move'). This makes it immediately distinguishable from sibling tools like compute_spot_prices, which would return current prices rather than alerts.

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 opens with an explicit 'Use compute_alerts when...' trigger, giving the agent a clear condition for selection. It then supplies the exact invocation details for this paid tool: POST JSON to paid_url with the x402 v2 PAYMENT-SIGNATURE header, cost, and supported networks.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All agent-embassy tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.