Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fotmob_league

Fetch FotMob league details: tabs, tables, fixtures, stats, transfers, seasons. Use /fotmob/seasons for valid season values; optional shot maps.

Instructions

FotMob league details and sections. Returns FotMob's public league page payload, including available tabs, overview, table, fixtures, statistics, transfers, and seasons where supplied by the league. Discover valid season values with /fotmob/seasons. shotmap=true includes the optional, larger overview shot-map payload.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
seasonNoOptional season value from /fotmob/seasons for this league
shotmapNoInclude the optional overview shot map; increases response size
league_idYesNumeric FotMob league id from /fotmob/leagues

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.6
    • addedInput schema / properties / season
      Added value: +{
+  "description": "Optional season value from /fotmob/seasons for this league",
+  "type": "string"
+}
    • addedInput schema / properties / shotmap
      Added value: +{
+  "description": "Include the optional overview shot map; increases response size",
+  "type": "boolean"
+}
  2. Addedv1.17.5

TDQS

A3.9/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 full burden and does well: it discloses the read-only nature, enumerates what is returned, notes conditional availability ('where supplied by the league'), and warns that shotmap=true produces a 'larger' payload. It omits auth/permission requirements and rate-limit or pagination behavior.

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?

Three tight sentences, front-loaded with what the tool returns and followed by the two actionable caveats (season discovery, shotmap size). Slight overlap with the schema's own parameter descriptions, but nothing is wasted or buried.

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?

There is no output schema, so the description reasonably compensates by enumerating the returned sections, and it covers both optional parameters. For a simple 3-param read tool this is nearly complete; only the conditional nature of several sections and any pagination/limits remain unstated.

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 description coverage is 100%, so the schema already documents all three parameters, including the /fotmob/seasons provenance for season and the size warning for shotmap. The description restates these almost verbatim rather than adding new syntax, format, or constraint detail, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('FotMob league details and sections') and enumerates the payload contents (tabs, overview, table, fixtures, statistics, transfers, seasons). It implicitly distinguishes itself from the section-specific siblings like fotmob_table or fotmob_transfers by describing itself as the aggregating page payload, though it never names those siblings explicitly.

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 clear routing guidance for the season parameter ('Discover valid season values with /fotmob/seasons'), pointing at the correct sibling for prerequisite data. It does not state when to prefer this aggregate tool over the narrower fotmob_table/fotmob_transfers/fotmob_stats siblings, so the routing is helpful but incomplete.

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