Skip to main content
Glama

Perp prices

get_prices
Read-only

Current perpetual prices and 24h change for up to 20 assets (crypto and US stocks), from Binance, Hyperliquid or Lighter.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbols": "<symbols>"
    },
    "name": "get_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolsYesTickers, e.g. ["BTC", "ETH", "TSLA"].

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the description's job is to add context beyond safety — and it does, disclosing that data is aggregated from three named venues and capped at 20 assets, which tells the agent the source is not selectable. It stops short of mentioning failure behavior for unknown or unsupported tickers, latency, or rate limits.

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?

One sentence, front-loaded with the returned data and followed by scope and sources. No filler and nothing that could be trimmed without losing meaning.

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?

For a one-parameter read tool with annotations supplied and no output schema, the description covers what is returned (price and 24h change), the input universe, and the data origin. What is missing — behavior on unknown symbols and whether a single source or a composite supplies each price — is minor but not trivial for a multi-venue aggregation 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 coverage is 100%: the single symbols parameter already carries a description, min/max items, and examples ("BTC", "ETH", "TSLA"). The description restates the 20-asset cap and clarifies the instrument universe (crypto and US stocks), but adds no new format or lookup semantics beyond the schema, so the 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?

The description names a concrete resource (current perpetual prices plus 24h change), its scope (up to 20 assets, crypto and US stocks), and its upstream sources. That is enough to separate it from siblings like get_funding_rates or get_oi_moves, though it never explicitly contrasts itself with them.

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?

When to use the tool is only implied by the phrase 'current perpetual prices' — there is no explicit trigger, no exclusions, and no mention of the sibling tools that return related derivatives data. Notably it does not explain how the Binance/Hyperliquid/Lighter source list is chosen, which an agent cannot control since there is no source parameter.

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