Skip to main content
Glama
leandersen

mcp-football

by leandersen

todays_matches

Fetch today's soccer matches: view schedule, scores, match status, and winner for top leagues and tournaments.

Instructions

This tool, todays_matches, sends a httpx get request to https://api.football-data.org/v4/matches, 
and pulls various data on todays soccer matches (games). This is good to use in case a user wants to know 
what the schedule and score of soccer games is today.

Available competitions: | WC | FIFA World Cup
                        | CL | UEFA Champions League
                        | BL1 | Bundesliga
                        | DED | Eredivisie
                        | BSA | Campeonato Brasileiro Série A
                        | PD | Primera Division
                        | FL1 | Ligue 1
                        | ELC | Championship
                        | PPL | Primeira Liga
                        | EC | European Championship
                        | SA | Serie A
                        | PL | Premier League

input: None
output: a list containing entries with info on home/away 
        team, score, date, status (game in play, timed, 
        finished), winner (None if not finished), the event 
        (like world cup), and current match day of the season/event.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description bears full burden. It discloses that it sends a GET request and returns specific fields, but lacks details on potential limitations like rate limits, authentication, or error handling.

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?

The description is well-structured with a main sentence followed by a list of competitions. It is somewhat lengthy but each part adds value, though it could be more concise.

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?

Given the tool's simplicity (no parameters, no nested objects), the description covers the purpose, output format, and available competitions. It is adequate for an agent to select and invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has no parameters, and the description explicitly notes 'input: None'. Schema coverage is 100%, so no additional parameter semantics needed.

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 clearly states the tool fetches soccer match data for today via an API call, listing output fields and available competitions, distinguishing it from the sibling tool competition_top_scorers.

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?

The description explicitly says it is useful when a user wants to know today's soccer schedule and scores. It does not state when not to use it or mention alternatives, but the sibling tool has a different purpose, so confusion is unlikely.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/leandersen/MCP-Football'

If you have feedback or need assistance with the MCP directory API, please join our Discord server