Crypto Bot Audit + Market Data (x402 paid)

Token price history

market_llama_asset_price_history

Read-onlyIdempotent

Hourly or daily USD price points for one token reference (network:address) from DefiLlama's coin API, with the symbol and confidence it attaches to the series. Costs $0.001 USDC per call. Byte-identical to GET /market/llama-asset-price-history?ref=coingecko:bitcoin&period=1h&span=20.

Input Schema

TableJSON Schema

Name	Required	Description
`ref`	Yes	asset reference as network:identifier [required]
`span`	No	how many points (max 720) (default 48)
`period`	No	point spacing (default "1h")

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ts`	No
`ref`	No
`note`	No
`count`	No
`found`	No
`stale`	No
`caveat`	No
`period`	No
`prices`	No
`reason`	No
`source`	No
`symbol`	No
`decimals`	No
`confidence`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 25, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "caveat": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "confidence": {
+      "type": "number"
+    },
+    "count": {
+      "type": "integer"
+    },
+    "decimals": {
+      "type": "integer"
+    },
+    "found": {
+      "type": "boolean"
+    },
+    "note": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "period": {
+      "type": "string"
+    },
+    "prices": {
+      "items": {},
+      "type": "array"
+    },
+    "reason": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "ref": {
+      "type": "string"
+    },
+    "source": {
+      "type": "string"
+    },
+    "stale": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "symbol": {
+      "type": "string"
+    },
+    "ts": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedSep 24, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world, and non-destructive behavior. The description adds valuable behavioral context beyond this: a per-call cost of $0.001 USDC, the DefiLlama API source, and byte-identical equivalence to a specific REST endpoint.

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 sentences, both necessary: the first front-loads the core output semantics, and the second adds cost and exact endpoint identity. There is no redundancy or filler.

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, return-value details are already covered. The description supplies the remaining operational context an agent needs: source, pricing, ref format, period granularity, and exact endpoint equivalence. Nothing essential is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds meaning by clarifying ref as 'network:address', explaining period via 'Hourly or daily', and providing a concrete example ref (coingecko:bitcoin) through the endpoint illustration.

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 clearly identifies the resource (one token reference from DefiLlama's coin API) and the output (hourly or daily USD price points, symbol, confidence). It is easily distinguished from siblings like market_llama_price_snapshot because of the explicit 'history' framing and the exact GET endpoint mapping.

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?

Usage context is implied: the tool is for historical hourly or daily USD price series for a single token reference. However, it does not explicitly say when to prefer this over alternatives such as market_llama_price_snapshot or get_token_price, nor does it state any exclusions.

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

All Crypto Bot Audit + Market Data (x402 paid) 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?