Crypto Bot Audit + Market Data (x402 paid)

Hyperliquid perp specifications

market_hl_perp_specs

Read-onlyIdempotent

Per-coin contract rules from Hyperliquid's own meta: size decimals, maximum leverage and the margin table id, for the whole listed universe or filtered by substring. Costs $0.001 USDC per call. Byte-identical to GET /market/hl-perp-specs?contains=PEPE&limit=20.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	coins to return (max 100) (default 25)
`contains`	No	case-insensitive substring filter on the coin name (default null)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ts`	No
`note`	No
`rows`	No
`count`	No
`stale`	No
`caveat`	No
`reason`	No
`source`	No
`universe`	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"
+      ]
+    },
+    "count": {
+      "type": "integer"
+    },
+    "note": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "reason": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "rows": {
+      "items": {},
+      "type": "array"
+    },
+    "source": {
+      "type": "string"
+    },
+    "stale": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "ts": {
+      "type": "string"
+    },
+    "universe": {
+      "type": "integer"
+    }
+  },
+  "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/non-destructive behavior. The description adds valuable non-obvious traits: a $0.001 USDC cost per call, the upstream source ('Hyperliquid's own meta'), and byte-identical equivalence to a specific REST endpoint. These go beyond the structured 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?

Three sentences, each earning its place: core purpose/data, cost, and endpoint equivalence. Front-loaded with the essential 'per-coin contract rules' and data fields before cost/source details.

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?

Given only two optional string parameters, an output schema, and read-only/idempotent annotations, the description covers everything an agent needs: data contents, filtering option, cost, and a byte-identical reference endpoint. No critical behavioral or input context 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 description coverage is 100%, so the schema already documents `limit` and `contains` with defaults, constraints, and case-insensitivity. The description reinforces substring filtering and shows a sample endpoint usage, but adds no materially new parameter semantics.

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?

Description states a specific resource ('Per-coin contract rules from Hyperliquid's own meta') and enumerates exact data fields: size decimals, maximum leverage, and margin table id. It also clearly defines the scope ('whole listed universe or filtered by substring'), which distinguishes it from sibling market_hl_* tools like market_hl_mid_price or market_hl_order_book.

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 provides clear context: use it when you need per-coin Hyperliquid perpetual contract rules, either for all listed coins or filtered by coin name substring. It doesn't explicitly name alternatives or exclusions, but its precise scope makes the appropriate use obvious.

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?