Skip to main content
Glama
Sign In
fotmob-mcp

fotmob-mcp

by MoRocety
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

search

Find football teams, players, leagues, or matches by name. Enter a search term to get matching FotMob results.

Instructions

Search FotMob for teams, players, leagues, or matches by name.

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": {
      "term": "<term>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
termYesSearch term, e.g. 'Arsenal' or 'Messi'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavior. It only says what it searches, not what results look like, whether it returns multiple matches, or any limitations (e.g., partial name matching). The agent has no information about response structure or potential ambiguity.

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?

One sentence, front-loaded with the main action. It is concise and covers the core purpose. Could be slightly more structured but is efficient.

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

Completeness2/5

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

Given the tool is a search function with no output schema and no annotations, the description is thin. It does not mention return format, result count, or how it handles no matches. For a search tool, this is insufficient context.

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% with a clear description of 'term' and an example. The description adds the list of entity types It does not add additional meaning beyond the schema, but the schema itself is sufficient.

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 searches FotMob for teams, players, leagues, or matches by name. This distinguishes it from sibling tools that retrieve specific entities by ID or date.

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 description implies use when finding an entity by name, but does not explicitly state when to use this versus direct lookups (e.g., get_team or get_player). It could mention that this is a discovery entry point before fetching details.

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