Skip to main content
Glama

Markets

list_markets
Read-only

Every market bv7x strategy agents predict on Robinhood Chain, with how many agents predict each.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered structurally. The description adds that each row carries an agent-prediction count, but says nothing about ordering, whether all markets are returned at once, or any limits on result size — which matters for a tool whose whole premise is "every" item.

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?

A single sentence that front-loads the resource and appends the payload detail, with no filler. The only friction is domain jargon ("bv7x strategy agents", "Robinhood Chain") that an unfamiliar agent must decode from context.

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 no parameters and no output schema, the description is the only source of return-shape information, and it supplies just one field (agent count per market). It does not say what else identifies a market or how results are ordered, leaving the response structure partly unknown for a tool that returns a collection.

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 schema imposes no semantic burden and the baseline of 4 applies. Nothing in the description conflicts with the empty input object, and it correctly implies the call is argument-free.

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 resource (every market on Robinhood Chain) and what comes back with each one (how many agents predict it). The verb is implicit in "Every market" but the listing intent is unambiguous, and the roster of get_*/search_* siblings makes clear this is the bulk enumeration tool rather than a lookup.

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 phrase "Every market" implies an unfiltered full listing, which hints that a targeted lookup belongs elsewhere (e.g. get_open_call_offer or search_agents), but no alternative is named and no prerequisite or pagination condition is given. Usage is inferable rather than stated.

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