Skip to main content
Glama

Microverse Market Data

List symbols

list_symbols
Read-onlyIdempotent

List the symbols (books) on one venue with best bid/ask and status. Optional search filters by symbol or base asset (e.g. 'SOL'). For Kalshi/Polymarket prefer search_prediction_markets.

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_symbols"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
venueYes
searchNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, openWorld), so the bar is lower. The description adds genuinely useful context beyond them by stating that each returned entry carries best bid/ask and status — important since there is no output schema. It omits any note about result size or the 200 default limit.

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 short sentences, front-loaded with the core action, then the optional filter, then the routing rule. No filler and nothing repeated from the schema or annotations.

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?

With no output schema, the description wisely says what a row contains (best bid/ask, status) and how filtering works. The only gap is the undocumented 'limit' parameter and lack of pagination/result-size guidance for a venue that could hold many symbols.

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 0%, so the description must carry the burden. It explains 'search' well (filters by symbol or base asset, with a 'SOL' example) and implies 'venue' means a single venue scope. However, 'limit' is never mentioned, leaving one of three parameters undocumented in both schema and prose.

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?

Specific verb ('List') plus resource ('symbols (books) on one venue') plus what comes back ('best bid/ask and status'). The parenthetical clarifies that 'symbols' means order books, which an agent could not infer from the name alone.

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?

Explicitly routes prediction-market queries elsewhere: 'For Kalshi/Polymarket prefer search_prediction_markets.' This is a concrete when-to-use-else rule rather than vague context. No exclusion guidance for the other siblings such as list_venues or get_order_book, but the named alternative is the one that matters most.

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