Skip to main content
Glama

Front of Goal

Find matches

find_matches
Read-onlyIdempotent

Find football (soccer) matches and their current market odds by team, league, or both. Returns each match's kickoff time (UTC), status, home/draw/away probabilities, a match_id and its frontofgoal.com page. Use it for questions like "when do Arsenal play next?", "what Premier League games are on this weekend?" or "what's on today?". With no team or league it lists the most-traded matches. Use when "recent" for results from the last three days.

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

Input Schema

NameRequiredDescriptionDefault
teamNoA team name as people say it, e.g. "Arsenal", "Man Utd", "Real Madrid", "PSG".
whenNoTime window. today and tomorrow are UTC days; live is matches in play; recent is the last three days.next_7_days
limitNoMost matches to return (1 to 25).
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").

Output Schema

NameRequiredDescriptionDefault
noteNoWhy the list is empty or cut short, and what to try.
filterNo
matchesYes
total_foundYesMatches found before the limit.
other_teams_with_that_nameNo

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, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: the fields returned (kickoff UTC, status, home/draw/away probabilities, match_id, page URL) and the fallback behavior when no filters are supplied. It says nothing about result caps beyond the schema's limit or about data freshness/rate limits, so the value added is moderate rather than rich.

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?

Four sentences, front-loaded with the core purpose and followed by return fields, use cases, and default behavior; nothing is padded. The trailing sentence ('Use when "recent" for results from the last three days') is slightly awkwardly phrased and largely restates the schema's enum description, a minor redundancy.

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, return values need not be explained, and the description still summarizes them helpfully; defaults, time-window semantics, and query patterns are all covered. The remaining gap is the lack of any routing statement relative to the odds-oriented siblings, which matters for a tool whose output overlaps with theirs.

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 parameter meaning is largely carried by the schema itself, including the when enum values and the limit range. The description contributes one extra semantic detail: that omitting team and league yields the most-traded matches, which is not derivable from the schema. That is a real but modest addition over an already complete schema, so the baseline 3 fits.

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 ('Find football (soccer) matches and their current market odds') and enumerates the filter axes (team, league, or both), so the agent knows what it retrieves. It stops short of differentiating from siblings like get_match_odds or get_market, which also deal with odds, leaving a small ambiguity about which tool to pick for a single-match odds lookup.

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 concrete invocation contexts via example questions ('when do Arsenal play next?', 'what Premier League games are on this weekend?') and explicitly states the no-filter default ('lists the most-traded matches'), plus a note on using when='recent' for results. It does not name an alternative tool or state when not to use this one, which keeps it below a 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.