Skip to main content
Glama

Front of Goal

Get match odds

get_match_odds
Read-onlyIdempotent

Current odds for one football match: home win, draw and away win as implied probabilities and decimal odds from a real-money prediction market, with kickoff time (UTC), venue when known, status, live score while in play, the result once finished, recent form and the match page link. Pass match_id from find_matches, or just a team name to get that team's next match. Prices are live when the market's feed answers (prices_live).

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

Input Schema

NameRequiredDescriptionDefault
teamNoInstead of match_id: a team name, to get that team's next match.
match_idNoThe match: an id from find_matches, list_futures or get_market, or a frontofgoal.com page URL.

Output Schema

NameRequiredDescriptionDefault
urlYesThe match page on frontofgoal.com.
awayYesAway team.
formNo
homeYesHome team.
noteNoCaveats about the prices or status.
oddsYes
scoreNoScore as home-away while in play or after the match, when known.
venueNo
minuteNoMatch minute while in play, when known.
resultNohome, draw or away once settled.
statusYesscheduled, in_play, finished, awaiting_result, postponed, cancelled, abandoned or suspended.
kickoffNoKickoff, ISO 8601 UTC.
match_idYesMatch id.
league_idNoLeague id.
competitionNoLeague or cup.
prices_liveNoTrue when the prices were read live for this answer.
other_marketsNo
traded_30d_usdNoUS dollars traded on this match in the last 30 days.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds genuinely new behavioral context: the response shape changes with match status (live score while in play, result once finished), venue is only present when known, and prices may be stale when the feed does not answer, surfaced via prices_live.

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?

Purpose and scope are front-loaded in the first clause, and the input routing plus the freshness caveat are ordered sensibly. The long enumeration of returned fields in the opening sentence is partly wasted since an output schema exists, but it is compact and not padded.

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, the definition needn't detail return values, and the annotations cover safety. The description covers inputs, source tools, status-dependent output behavior and the live-price caveat. Only edge cases such as ambiguous team names or missing fixtures go unaddressed.

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 both parameters are already documented, and the description's restatement that a team name returns that team's next match largely duplicates the schema text. Its only added value is the sourcing hint that match_id comes from find_matches, which is marginal beyond the structured field.

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?

The description opens with a specific verb and resource ("Current odds for one football match"), names the three markets returned, and identifies the data source as a real-money prediction market. It also implicitly separates itself from find_matches (which supplies ids) and get_market, so an agent can pick it without opening the schema.

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?

It gives concrete entry paths: pass a match_id sourced from find_matches, or a team name to resolve that team's next match. That is real when-to-use guidance with a sibling dependency spelled out. It stops short of explicit exclusions (e.g. what to do when a team name is ambiguous or has no upcoming fixture).

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.