Agent Embassy

Compute Alerts

compute_alerts

Idempotent

GPU price moves that matter: significant spot moves, in a signed receipt. limit defaults to 25. Live snapshot: compute_spot_prices. Past: compute_history. 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

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: 8-128 printable ASCII characters (no spaces), client-generated, one per logical request — a UUID v4 is recommended. 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

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. check_url_custom
`asset`	Yes	Settlement asset
`price`	Yes	Exact price, e.g. "$0.25"
`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.

Changed1 schema field changedNov 3, 2026

changedInput schema / properties / idempotency_key / description

Previous 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."New value: +"Idempotency key: 8-128 printable ASCII characters (no spaces), client-generated, one per logical request — a UUID v4 is recommended. 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."

Changed1 schema field changedOct 23, 2026
- changedOutput schema / properties / price / description
```
Previous value: -"Exact price, e.g. \"$0.05\""New value: +"Exact price, e.g. \"$0.25\""
```
Changed1 schema field changedOct 17, 2026
- changedOutput schema / properties / tool / description
```
Previous value: -"Tool name, e.g. ping"New value: +"Tool name, e.g. check_url_custom"
```
Changed1 schema field changedOct 15, 2026
- changedOutput schema / properties / price / description
```
Previous value: -"Exact price, e.g. \"$0.15\""New value: +"Exact price, e.g. \"$0.05\""
```
Changed1 schema field changedOct 15, 2026
- changedOutput schema / properties / tool / description
```
Previous value: -"Tool name, e.g. verified_check"New value: +"Tool name, e.g. ping"
```

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"

First observedSep 23, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations only declare safety/idempotency flags; the description adds substantial context they don't carry — that this is a paid POST to a specific paid_url, requires an x402 v2 PAYMENT-SIGNATURE header, costs $0.25 in USDC on Base or Arbitrum One, and returns a signed receipt. That is the exact information an agent needs before committing funds. It stops short of covering payment-failure or rate-limit behavior.

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?

It is short and front-loads the purpose, then alternatives, then payment mechanics, which matches the order an agent needs. Minor waste remains in the promotional phrasing 'price moves that matter' and the trailing bare URL after the paid_url has already been given.

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 paid, non-read-only tool, the description covers purpose, sibling routing, cost and currency, payment protocol, and the exact paid endpoint; parameters are fully covered by the schema and an output schema exists so return values needn't be described. An agent has everything required to invoke it correctly, including the payment step.

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 description coverage is 100%, so the schema already documents gpu, limit and idempotency_key in detail. The description only restates 'limit defaults to 25', which duplicates the schema rather than adding meaning, so the baseline 3 applies.

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

Purpose4/5

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

The description states a specific resource and output shape: 'GPU price moves that matter: significant spot moves, in a signed receipt.' Combined with the routing lines ('Live snapshot: compute_spot_prices. Past: compute_history') an agent can place it precisely among siblings, though the headline phrase 'that matter' is marketing wording rather than a crisp verb.

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

Usage Guidelines4/5

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

It explicitly names the two alternative tools and the conditions that select them: live snapshot versus past history, with this tool covering significant moves. There is no explicit 'do not use when' statement, so it falls short of a full 5, but the routing guidance is concrete and actionable.

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.

Resources

Need Help?