Skip to main content
Glama

Front of Goal

List futures markets

list_futures
Read-onlyIdempotent

Season-long and tournament markets (futures/outrights) such as league winner, top scorer, relegation, top-four finish or cup winner, with the likeliest outcomes and their implied probabilities. Filter by league and by words in the market title. Use for questions like "who is favourite to win the Premier League?" or "Champions League winner odds".

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

Input Schema

NameRequiredDescriptionDefault
limitNoMost markets to return (1 to 20).
queryNoWords in the market title, e.g. "winner", "top scorer", "relegated".
leagueNoA league or cup: its id from list_leagues (e.g. "premier-league"), its name ("La Liga") or a common short name ("EPL", "UCL", "MLS").
outcomes_per_marketNoLikeliest outcomes to show per market (1 to 10). get_market lists more.

Output Schema

NameRequiredDescriptionDefault
noteNoWhy the list is empty or cut short.
queryNoThe title filter used.
leagueNo
marketsYes
total_foundYesMarkets found before the limit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, open-world, non-destructive, so the safety profile is covered. The description adds that results include the likeliest outcomes with their implied probabilities, which is useful context beyond the annotations. It does not cover pagination or how many markets exist in total, leaving further behavioral detail to the output schema.

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 sentences: the first front-loads what the tool returns and its filterability, the second gives usage triggers. Every clause carries information and nothing is padded, though the parenthetical '(futures/outrights)' is slightly redundant with the tool name.

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 an output schema present and full parameter coverage, the description only needs to establish scope and when to use it, which it does. Minor gap: it doesn't hint at result volume or what 'implied probabilities' represent in practice, but nothing required for correct invocation is missing.

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 100%, so all four parameters (limit, query, league, outcomes_per_market) are already documented in detail, including formats and ranges. The description only restates that filtering is by league and title words, adding no syntax or edge-case meaning 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?

Names a specific verb+resource ('Season-long and tournament markets (futures/outrights)') and enumerates concrete market types (league winner, top scorer, relegation, top-four finish, cup winner), so the scope is unmistakable. It does not explicitly contrast itself with get_market or list_leagues, so it falls short of the sibling-differentiating bar for 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides concrete when-to-use triggers via example questions ('who is favourite to win the Premier League?', 'Champions League winner odds') plus the filter conditions (league, title words). No explicit exclusions or pointer to get_market for deeper detail, so no 5.

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.