Skip to main content
Glama

Front of Goal

Get market odds

get_market
Read-onlyIdempotent

Every outcome of one market with its implied probability, decimal odds and whether it is taking bets: a futures market (e.g. league winner), a side market on a match (exact score, half-time result) or a match itself. Pass a market_id from list_futures, find_matches or get_match_odds. Shows the winner once the market has settled.

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": {
      "market_id": "<market_id>"
    },
    "name": "get_market"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMost outcomes to return, likeliest first (1 to 40).
market_idYesThe market: an id from find_matches, list_futures or get_market, or a frontofgoal.com page URL.

Output Schema

NameRequiredDescriptionDefault
urlYesMarket page on frontofgoal.com.
noteNoCaveats about the prices.
typeNomatch or futures.
teamsNo
titleYesMarket title.
statusYesopen or closed.
winnerNoThe winning outcome once settled.
outcomesYes
league_idNoLeague id.
market_idYesMarket id.
competitionNoLeague or cup.
prices_liveNoTrue when the prices were read live for this answer.
outcome_countNoOutcomes in total.
traded_30d_usdNoUS dollars traded in the last 30 days.
kickoff_or_closeNoKickoff for a match, or when a futures market settles at the latest; ISO 8601 UTC.

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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description does add real context beyond that: outcomes include implied probability and betting status, and once a market settles the winner appears. It does not discuss data freshness or what an unsettled/inactive market looks like.

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?

Three dense sentences with no filler, front-loaded on what the tool returns. The middle sentence about id sourcing sits naturally before the settlement note, giving a sensible read order.

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 rich annotations, the description need not explain return values, and it still covers market types, id sourcing and settlement behavior. Only the distinction from get_match_odds is left implicit, which is a small gap for a two-parameter read tool.

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 100%, with market_id documented as an id from find_matches, list_futures or get_market, or a frontofgoal.com URL, and limit documented as likeliest-first with a 1-40 range. The description restates the id sourcing and the 'likeliest first' ordering rather than adding new meaning, so baseline 3 is appropriate.

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 verb and resource ('Every outcome of one market') plus exactly what each outcome carries: implied probability, decimal odds and whether it is taking bets. It enumerates market shapes (futures, side market, match itself) which helps distinguish scope from a single-match odds lookup, though it never explicitly contrasts itself with get_match_odds.

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?

Gives a concrete precondition for use: obtain a market_id from list_futures, find_matches or get_match_odds, which tells the agent the upstream call sequence. It stops short of stating when to prefer this over get_match_odds, so there is no explicit alternative routing.

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.