Skip to main content
Glama

agent-embassy

by io.github.tacticalnoot
OverviewDiscussionsAdmin

Compute History

compute_history
Idempotent

GPU market memory: cheapest and median asks per class, in a signed receipt. limit defaults to 50. Live: compute_spot_prices. Moves: compute_alerts. 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

NameRequiredDescriptionDefault
gpuNoOptional GPU filter, e.g. 'H100 SXM' (max 64 chars). Omit for whole-market history
limitNoMax history points to return; integer 1-200. Defaults to 50
idempotency_keyYesIdempotency 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

NameRequiredDescriptionDefault
howYesHow to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header
toolYesTool name, e.g. check_url_custom
assetYesSettlement asset
priceYesExact price, e.g. "$0.25"
networksYesEVM CAIP-2 network ids accepted
paid_urlYesx402-paid HTTPS URL to POST the tool inputs to
facilitatorYesx402 facilitator
payment_requiredYesAlways true: this MCP tool is a payment pointer; the tool itself is monetized via x402.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / price / description
      Previous value: -"Exact price, e.g. \"$0.05\""New value: +"Exact price, e.g. \"$0.25\""
  2. Changed1 schema field changed
    • changedOutput schema / properties / tool / description
      Previous value: -"Tool name, e.g. ping"New value: +"Tool name, e.g. check_url_custom"
  3. Changed1 schema field changed
    • changedOutput schema / properties / price / description
      Previous value: -"Exact price, e.g. \"$0.15\""New value: +"Exact price, e.g. \"$0.05\""
  4. Changed1 schema field changed
    • changedOutput schema / properties / tool / description
      Previous value: -"Tool name, e.g. verified_check"New value: +"Tool name, e.g. ping"
  5. Changed2 schema fields changed
    • 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."
  6. Changed4 schema fields changed
    • 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"
  7. Changed4 schema fields changed
    • 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)."
  8. Changed1 schema field changed
    • 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."
  9. Changed1 schema field changed
    • 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"
+}
  10. Changed4 schema fields changed
    • 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)."
  11. Added

TDQS

A3.8/5.0
Behavior3/5

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

The description adds real behavioral context beyond annotations: a paid POST to a specific paid_url with an x402 v2 PAYMENT-SIGNATURE header, $0.25 in USDC on Base or Arbitrum One, plus a docs link. That explains why readOnlyHint is false despite the tool being a data read. It does not discuss what happens on payment failure / insufficient funds or the receipt's verification semantics, which is the main remaining gap for a paid endpoint.

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?

Front-loaded with purpose, then alternatives, then payment mechanics and endpoint — a sensible information order with no wasted clauses. The fragmentary, colon-separated style is compact but slightly reads as notes rather than prose, which costs a point.

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?

Everything an agent needs to invoke it is present: endpoint URL, transport (POST JSON), auth header scheme, price and chains, plus sibling routing. Return values are covered by the output schema and parameters by the 100%-covered input schema, so no further description content is required.

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%, including the idempotency_key replay semantics, so the schema already carries parameter meaning. The description only restates the 'limit defaults to 50' default and adds no filtering/syntax detail for gpu beyond what the schema provides. 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?

States the resource precisely (GPU market history: cheapest and median asks per class, delivered as a signed receipt) and names the sibling it must not be confused with (compute_spot_prices for live data). The telegraphic 'GPU market memory' opener lacks an explicit verb, but the following colon phrase removes any ambiguity about what is returned.

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?

Routing is explicit via 'Live: compute_spot_prices. Moves: compute_alerts.', which tells the agent which sibling to pick for the other two data shapes. It stops short of an explicit exclusion sentence such as 'do not use for real-time quotes', but the contrast is clear enough to act on.

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

All agent-embassy toolsInspect
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