Skip to main content
Glama

Agent Exchange store

perps_mids

$0.002 via x402: Mid prices for every Hyperliquid market (about 1,300 incl. spot) or a comma list of coins, with the server timestamp. Pay 0.002 USDC through https://store.agentexchange.work/gw/perps/mids?coins=BTC,ETH,SOL Via the Agent Exchange store gateway; settled by Coinbase.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "perps_mids"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinsNocomma list; empty = all
x_paymentNoSigned x402 payment payload (optional; without it the answer is the price)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the x402 paywall, the exact cost ($0.002 USDC), the gateway endpoint, that settlement is via Coinbase, and that a server timestamp is returned. It omits rate limits and the unauthenticated response shape, but payment behavior — the critical trait here — is fully surfaced.

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 the core purpose in the first sentence, then payment mechanics. The '$0.002 via x402' framing and the full gateway URL are somewhat redundant with the 'Pay 0.002 USDC through...' clause, but every element is functional and the paragraph stays tight.

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?

No output schema and no annotations, yet the description covers what an agent needs: what it returns (mid prices), the universe size, the timestamp field, and the payment flow including the optional x_payment payload. Only the response format for unpaid calls is left to the schema note.

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%, so the schema already documents both 'coins' (comma list; empty = all) and 'x_payment'. The description reinforces the comma-list usage and states market coverage (~1,300), which is useful context, but adds no format or syntax detail beyond the schema. 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 a specific verb+resource: 'Mid prices for every Hyperliquid market... or a comma list of coins, with the server timestamp.' This clearly separates it from siblings like perps_funding and perps_market by naming mid prices and market coverage. It does not explicitly name those siblings, but the resource is unambiguous.

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

Usage Guidelines2/5

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

There is no when-to-use guidance or exclusions. The description implies scope ('every Hyperliquid market' vs a comma list of coins) but never says when to prefer this over perps_market or perps_funding, nor what the empty-coins default means beyond the schema note.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources