Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fotmob_seasons

Discover FotMob seasons for a league by numeric league_id; pass a valid season to the league endpoint to query league data.

Instructions

FotMob league season discovery. Lists the season values FotMob offers for one league, identified by the required numeric league_id (from the FotMob leagues endpoint). The response has the league id, name and a seasons list such as 2026/2027. Pass a season to the FotMob league endpoint; the list varies by league.

Input Schema

NameRequiredDescriptionDefault
league_idYesNumeric FotMob league id from /fotmob/leagues

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.6

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden, and it does disclose the response shape (league id, name, and a `seasons` list like `2026/2027`) plus the key behavioral trait that 'the list varies by league.' It omits auth/permission and rate-limit context, but for a read-only discovery endpoint this is solid disclosure.

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?

Three sentences, front-loaded with the purpose, then the input provenance, then the output and downstream use. No filler or redundancy.

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?

With no output schema and no annotations, the description covers what the tool returns, where the input comes from, and how the result feeds the next call. Nothing essential to invoking it correctly is missing.

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% and the single parameter already documents itself as the numeric FotMob league id from /fotmob/leagues. The description restates required/numeric and the origin endpoint but adds no syntax, range, or format detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource: 'Lists the season values FotMob offers for one league.' It scopes to a single league and names the identifier, letting an agent distinguish it from sibling league tools such as fotmob_leagues and fotmob_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?

Explains where the league_id comes from ('from the FotMob leagues endpoint') and how the output is consumed ('Pass a season to the FotMob league endpoint'), which is real chaining guidance. It does not state when not to use this tool or name explicit alternatives, so it stops short of a 5.

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