Skip to main content
Glama

PerpMetric perpetuals data

List instruments

list_instruments
Read-onlyIdempotent

Instrument universe for a venue: symbols and ids you can pass to other tools. Optional prefix search.

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": {
      "venue": "<venue>"
    },
    "name": "list_instruments"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
venueYesExchange. hyperliquid = Hyperliquid (Core + HIP-3), aster = Aster, lighter = Lighter.
searchNoOptional symbol prefix, e.g. 'BT'.
market_setNoHyperliquid only: core perps or HIP-3 builder-deployed markets (e.g. xyz:TSLA). Ignored for other venues.core

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered. The description adds genuinely useful context that results are identifiers consumable by other tools, but says nothing about result size, paging, or the venue-specific market_set behavior.

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?

Two short sentences with the resource and output utility front-loaded; every phrase carries information. It is efficient, though the leading noun phrase reads slightly telegraphic rather than as a clean purpose statement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With four parameters, no output schema, and rich annotations, the description is serviceable but omits two things an agent would want: that market_set applies only to Hyperliquid and is ignored elsewhere, and that results are capped by a limit with a default of 200. Both are recoverable from the schema, so the gap is moderate rather than severe.

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 75% and both enums (venue, market_set) plus 'search' are documented inline with examples, so the schema carries the parameter burden. The description only restates the prefix-search behavior already in the schema and adds no new meaning.

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 identifies the resource (instrument universe for a venue) and its output value ('symbols and ids you can pass to other tools'), which implicitly separates it from market-data siblings like get_markets or get_breadth. It uses a noun phrase rather than an explicit verb ('List'), so it is clear but slightly clipped.

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?

'Optional prefix search' hints at the lookup use case, and 'pass to other tools' implies this is the discovery step before calling symbol-based tools. However, it never states when to choose this over get_markets or compare_venues, nor any explicit exclusions.

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