Skip to main content
Glama

Microverse Market Data

List venues

list_venues
Read-onlyIdempotent

List every venue (exchange or market) with how many books we carry, how many are live, and whether history is available. Use the venue ids it returns in the other tools.

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": "list_venues"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered externally. The description adds value by disclosing the shape of what comes back (per-venue book counts, live counts, history flag), which annotations cannot express. It still says nothing about pagination, ordering, or whether the list can be large.

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?

Two sentences, both front-loaded with the payload description first and the follow-up usage note second. Every clause carries information: what is listed, what fields accompany each item, and what the ids are good for.

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 carries the burden of explaining returns, and it does so at a reasonable level (counts of books, live books, history availability). For a zero-parameter, annotation-covered read tool this is nearly sufficient; only field naming and ordering conventions are left unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline of 4 applies; there is no parameter semantics to compensate for. The description correctly implies the tool is filterless and returns the full venue set.

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 gives a specific verb and resource, 'List every venue (exchange or market)', and even clarifies what a venue is and what attributes accompany each entry (book counts, live counts, history availability). It does not explicitly distinguish itself from siblings such as compare_venues, so it falls short of a 5.

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?

The second sentence, 'Use the venue ids it returns in the other tools', gives useful follow-on guidance about how the output feeds other tools, which implies this is a discovery step. However, it never states when to prefer this over compare_venues or other siblings, nor does it set any exclusion conditions.

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