Crypto Bot Audit + Market Data (x402 paid)

Jupiter USD prices by mint

market_jup_token_prices

Read-onlyIdempotent

Current USD price, 24h change, liquidity, decimals and the block the quote came from for up to 20 Solana mints, in one call — with an explicit list of which mints returned nothing. Costs $0.001 USDC per call. Byte-identical to GET /market/jup-token-prices?mints=So11111111111111111111111111111111111111112,EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`mints`	Yes	comma list of up to 20 Solana token mints [required]

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ts`	No
`note`	No
`found`	No
`stale`	No
`caveat`	No
`priced`	No
`prices`	No
`reason`	No
`source`	No
`notPriced`	No
`requested`	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"
+      ]
+    },
+    "found": {
+      "type": "boolean"
+    },
+    "notPriced": {
+      "items": {},
+      "type": "array"
+    },
+    "note": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "priced": {
+      "type": "integer"
+    },
+    "prices": {
+      "additionalProperties": {},
+      "type": "object"
+    },
+    "reason": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "requested": {
+      "type": "integer"
+    },
+    "source": {
+      "type": "string"
+    },
+    "stale": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "ts": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedSep 24, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already establish read-only, idempotent, and non-destructive behavior. The description adds meaningful behavioral context beyond that: the exact fields returned, the explicit missing-mint list, the per-call cost, and byte-identical equivalence to a REST endpoint. No contradictions with annotations.

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?

The description is a single dense sentence that front-loads the returned fields and batch scope, then adds cost and endpoint equivalence. Every clause carries useful information, with no filler or repetition.

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 one-parameter tool with a rich output schema and strong annotations, the description covers all essential operational details: what is returned, the batch limit, missing-mint behavior, cost, and REST equivalence. Nothing an agent needs to invoke it correctly is missing.

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 coverage is 100% and the single parameter is already well described as a comma-separated list of up to 20 Solana token mints. The description reinforces this with concrete example mints, but does not add substantial new parameter semantics beyond the schema.

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 names the exact resource (Jupiter USD prices by Solana mint), the specific data returned (price, 24h change, liquidity, decimals, quote block), and the batching scope (up to 20 mints). It clearly distinguishes itself from single-token price tools by emphasizing the batch call and explicit missing-mint reporting.

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 makes the usage context clear: use this when you need current USD prices and related fields for up to 20 Solana mints in one call. It does not explicitly name alternatives or exclusion criteria, but the batch-oriented framing and cost disclosure imply when this tool is appropriate.

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?