Skip to main content
Glama
Sign In
fotmob-mcp

fotmob-mcp

by MoRocety
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_match_details

Get detailed match information including lineups, stats, events, and final score by supplying a FotMob match ID.

Instructions

Get detailed info for a single match: lineups, stats, events, and score.

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": {
      "matchId": "<matchId>"
    },
    "name": "get_match_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
matchIdYesFotMob match ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the transparency burden. It communicates a read-only lookup via 'Get' and specifies the main content categories returned. It does not cover error behavior or prerequisites, but for a simple single-ID read tool this is reasonably transparent.

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 sentence, front-loaded with the action and resource, and contains no filler or redundant phrasing. Every word contributes to understanding the tool's purpose.

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?

For a low-complexity tool with one parameter and no output schema, the description is largely complete: it identifies the resource and what the returned details include. It could mention that matchId may come from get_matches_by_date or address missing-match behavior, but these are minor gaps.

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 already describes matchId as a 'FotMob match ID' with 100% coverage. The description adds no extra semantic detail about the parameter beyond referencing a single match, so it meets the baseline without exceeding it.

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 retrieves detailed info for a single match, enumerating lineups, stats, events, and score. This distinguishes it from siblings like get_matches_by_date (date-based listing), get_team, get_player, and get_league.

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 phrase 'for a single match' makes the use case clear: call this when a specific match ID is already known and full match-level detail is needed. It does not explicitly name alternatives, but the contrast with list-oriented siblings is evident.

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

Deploy Server

Other Tools