fotmob-mcp

get_matches_by_date

Retrieve all football matches across leagues scheduled on a specific date. Provide the date in YYYYMMDD format to get the complete match list.

Instructions

Get all football matches (across leagues) scheduled on a given date.

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": {
      "date": "<date>"
    },
    "name": "get_matches_by_date"
  }
}

Input Schema

Name	Required	Description	Default
`date`	Yes	Date in YYYYMMDD format, e.g. 20260821

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 22, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations provided, the description carries the burden of explaining behavior. It clearly conveys that this is a read-only lookup of all matches on a date, but does not disclose other details such as match status, ordering, pagination, or coverage limitations.

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

Conciseness5/5

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

The description is one concise, well-structured sentence with no filler. It front-loads the action and resource and includes meaningful scope qualifiers ('across leagues', 'scheduled on a given date').

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter query tool with no output schema or annotations, the description provides sufficient context. It tells the agent exactly what the tool retrieves and how the result set is scoped, making the tool usable without further detail.

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?

The input schema fully describes the single date parameter with format and example, so the description does not need to add much. The tool description's 'given date' merely restates the parameter's purpose without adding extra semantic meaning.

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 uses a specific verb ('Get') and a clear resource ('all football matches across leagues') with an explicit temporal filter ('scheduled on a given date'). The phrase 'across leagues' helps distinguish it from sibling tools like get_match_details, which focuses on a single match.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The intended use is implied: querying matches by date across all leagues. However, the description does not explicitly provide when/when-not guidance or mention alternatives such as get_match_details for individual matches or search for broader queries.

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

Deploy Server