Skip to main content
Glama

AgentIndex x402

by world.agentindex
OverviewDiscussionsAdmin

Crypto Price

crypto
Read-onlyIdempotent

Live spot prices for crypto coins (BTC, ETH, SOL, ...) in USD or another fiat, with 24h change. Accepts tickers or CoinGecko ids. Try GET /crypto/sample.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
coinsYesCoin tickers (btc, eth, sol) and/or CoinGecko ids. String, comma-separated string, or array. Up to 20.
vs_currencyNoFiat quote currency, default usd (also eur, gbp, ...).usd

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pricesYes
vs_currencyYes
x402_receiptNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / coins / description
      Added value: +"Coin tickers (btc, eth, sol) and/or CoinGecko ids. String, comma-separated string, or array. Up to 20."
    • addedInput schema / properties / vs_currency / description
      Added value: +"Fiat quote currency, default usd (also eur, gbp, ...)."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "prices": {
+      "items": {
+        "properties": {
+          "change_24h_pct": {
+            "type": "number"
+          },
+          "id": {
+            "type": "string"
+          },
+          "price": {
+            "type": "number"
+          },
+          "symbol": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "vs_currency": {
+      "type": "string"
+    },
+    "x402_receipt": {
+      "type": "object"
+    }
+  },
+  "required": [
+    "vs_currency",
+    "prices"
+  ],
+  "type": "object"
+}
  2. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered. The description adds that prices are live and include 24h change, which is useful output context, but it says nothing about rate limits, error behavior for unknown tickers, or partial-failure handling for a multi-coin request.

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?

Two tight sentences with no filler, and the core capability (live spot prices + 24h change) is front-loaded before the accepted identifier forms and the sample hint.

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?

An output schema exists, so return-value documentation is unnecessary, and the annotations cover safety. The description covers what is queried and in what currencies; only failure modes and the multi-coin limit (which the schema handles) are left implicit, so it is nearly complete for this simple tool.

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%: the schema documents both coins (tickers/CoinGecko ids, formats, up-to-20 cap) and vs_currency (default usd, other fiats). The description's 'Accepts tickers or CoinGecko ids' and 'USD or another fiat' merely restate the schema, so the baseline of 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 names a specific resource and verb-equivalent ('Live spot prices for crypto coins ... in USD or another fiat, with 24h change'), making the tool's output scope unambiguous. It does not explicitly distinguish itself from the nearby gas_price sibling, but the resource (coin spot prices) is distinct enough that confusion is unlikely.

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

Usage Guidelines3/5

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

'Try GET /crypto/sample' hints at how to explore the endpoint, and the coin/currency framing implies the usage context. However, there is no explicit when-to-use vs when-not guidance and no named alternative (e.g., gas_price) is referenced, leaving the agent to infer selection.

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

All AgentIndex x402 toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources