agent-embassy

Compute History

compute_history

Idempotent

Use compute_history when you need GPU compute market history: a bounded time series of per-GPU cheapest/median/offer counts — or whole-market history when no GPU is named — sealed into your signed receipt. Prices are ephemeral asks, never delivered-cost guarantees. 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/history.

Input Schema

TableJSON Schema

Name	Required	Description
`gpu`	No	Optional GPU filter, e.g. 'H100 SXM' (max 64 chars). Omit for whole-market history
`limit`	No	Max history points to return; integer 1-200. Defaults to 50
`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 whole-market history"

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 history points to return; integer 1-200. Defaults to 50"

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 whole-market history."

removedInput schema / properties / idempotency_key / description

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

removedInput schema / properties / limit / description

Removed value: -"Max snapshots returned, 1-200 (default 50, oldest-first)."

Changed1 schema field changedSep 21, 2026

changedInput schema / properties / gpu / description

Previous value: -"GPU class, e.g. 'H100 SXM'. Omit for whole-market history."New value: +"Class, e.g. 'H100 SXM'. Omit for whole-market history."

Changed1 schema field changedSep 21, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "asset": {
+      "description": "Settlement asset",
+      "type": "string"
+    },
+    "facilitator": {
+      "description": "x402 facilitator",
+      "type": "string"
+    },
+    "how": {
+      "description": "How to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header",
+      "type": "string"
+    },
+    "networks": {
+      "description": "EVM CAIP-2 network ids accepted",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "paid_url": {
+      "description": "x402-paid HTTPS URL to POST the tool inputs to",
+      "type": "string"
+    },
+    "payment_required": {
+      "const": true,
+      "description": "Always true: this MCP tool is a payment pointer; the tool itself is monetized via x402.",
+      "type": "boolean"
+    },
+    "price": {
+      "description": "Exact price, e.g. \"$0.15\"",
+      "type": "string"
+    },
+    "tool": {
+      "description": "Tool name, e.g. verified_check",
+      "type": "string"
+    }
+  },
+  "required": [
+    "payment_required",
+    "tool",
+    "paid_url",
+    "price",
+    "networks",
+    "asset",
+    "facilitator",
+    "how"
+  ],
+  "type": "object"
+}

Changed4 schema fields changedSep 21, 2026

addedInput schema / properties / agent_wallet / description

Added value: +"DEV MODE ONLY: wallet to attribute. In live mode the payer wallet from the verified x402 payment is used."

addedInput schema / properties / gpu / description

Added value: +"GPU class, e.g. 'H100 SXM'. Omit for whole-market history."

addedInput schema / properties / idempotency_key / description

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

addedInput schema / properties / limit / description

Added value: +"Max snapshots returned, 1-200 (default 50, oldest-first)."

AddedSep 21, 2026

TDQS

A4.4/5.0

Behavior5/5

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

The description adds substantial behavioral context beyond the annotations: it discloses that this is a paid tool ($0.25 USDC on Base or Arbitrum One), requires an x402 v2 PAYMENT-SIGNATURE header, returns a signed receipt, and enforces idempotency-key replay semantics. It also clarifies that prices are ephemeral asks, not delivered-cost guarantees. This is consistent with the idempotentHint=true annotation and adds meaningful operational detail.

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 description is front-loaded with the core purpose and then efficiently covers payment, idempotency, and data semantics. It is somewhat dense and includes a placeholder-like 'paid_url' reference alongside the explicit paid URL, but every sentence contributes necessary operational information without significant waste.

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, idempotent market-history tool with an output schema, the description is remarkably complete. It covers what the tool returns, how to invoke it (POST, header, URL), payment terms, idempotency behavior, and the ephemeral nature of prices. An agent has everything needed to call it correctly.

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 all three parameters thoroughly. The description adds useful context like 'per-GPU cheapest/median/offer counts' and 'whole-market when no GPU is named,' but it does not substantially extend the parameter-level meaning beyond what the schema provides. Baseline 3 is appropriate.

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 opens with a specific verb and resource: 'Use compute_history when you need GPU compute market history.' It clearly defines the output as a bounded time series of per-GPU cheapest/median/offer counts, and distinguishes the whole-market variant when no GPU is named. This goes well beyond the generic title and differentiates it from sibling tools like compute_spot_prices.

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?

The description states when to use the tool ('when you need GPU compute market history') and provides a clear branching condition ('whole-market history when no GPU is named'). It does not explicitly name alternatives or state when not to use it, but the context is clear enough for an agent to select it appropriately.

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.