SiteCheck Agent Intel & Dev

European football match results with statistics and betting

dev_football_data_couk

Read-only

European football match results with statistics and betting odds from Football-Data.co.uk (free CSV data): for a league and season — date, kick-off, teams, full-time and half-time score, result, referee, shots, shots on target, corners, fouls, cards, plus market average and Bet365 1X2 odds and average over/under 2.5 odds. 20 leagues (Premier League, La Liga, Bundesliga, Serie A, Ligue 1, Süper Lig…). Filter by team. Related tools on this server, for a different need: dev_pro_football_reference when you need NFL player season statistics, sorted leaderboard: per; dev_espn_college_football when you need ESPN college football scoreboard for one date: every game. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": {
      "league": "<league>"
    },
    "name": "dev_football_data_couk"
  }
}

Input Schema

Name	Required	Description
`team`	No	Only matches of this team (as spelled by the source, e.g. Man City)
`limit`	No	Matches, 1 to 400 (default 50), newest first
`league`	Yes	League code: E0, E1, E2, E3, EC, SC0, SC1, D1, D2, I1, I2, SP1, SP2, F1, F2, N1, B1, P1, T1, G1 (E0 = Premier League)
`season`	No	Season start year, e.g. 2025 for 2025/26 (default: current season)

Output Schema

Name	Required	Description	Default
`league`	No
`season`	No
`source`	No
`matches`	No
`results`	No
`checkedAt`	No
`leagueName`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds real operational context beyond them: a per-call price of $0.002 USDC via x402 on Base/Solana/Arc, and the fact that failed calls are not charged. It also discloses the underlying data source is free CSV, implying historical rather than live coverage. Rate limits and update cadence are not stated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and source are front-loaded, which is good, but the definition is one dense run-on block: the long stat enumeration (referee, shots on target, corners, fouls, cards, market average, Bet365 odds…) crowds out the more decision-relevant pricing and routing information. It could be restructured into scope / coverage / pricing lines.

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 described, and annotations carry the safety profile. The description covers source, coverage breadth, filtering, pricing and payment chain, which is most of what an agent needs to call this correctly. Only the relationship to closer sibling football-data tools is left unexplained.

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%, so the schema already documents team, limit, league codes and season. The description adds marginal value by naming the 20 covered leagues and one example (Premier League), but it does not map the code list beyond that or explain season semantics beyond what the schema states. Baseline 3 applies.

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?

States a specific verb+resource (match results with statistics and betting odds) plus the exact source (Football-Data.co.uk free CSV), the scope (a league and season), and an enumerated field list covering scores, shots, cards and 1X2 / over-under 2.5 odds. An agent can tell this is historical European league results data, not live scores or NFL data.

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 usage condition ('for a league and season', 'Filter by team') and explicitly routes to two alternatives for different needs. The gap: the alternatives named are NFL and college football, while the genuinely competing siblings on this server (dev_fbref, dev_flashscore, dev_sofascore_live, dev_understat_xg) are never mentioned, so an agent has no guidance on when to prefer this CSV source over those.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SiteCheck Agent Intel & Dev tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?