Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fotmob_stats

Fetch ranked FotMob player or team statistics for a league, season, and stat id, with optional team and position filters.

Instructions

FotMob league player or team statistics. Returns ranked player or team statistics for a stat id discovered from /fotmob/stats-categories. The accepted stat ids vary by league, season, and type. team_id optionally restricts player statistics to one team. position filters player results client-side.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statYesStat id returned by /fotmob/stats-categories for this league, season, and type
typeYesStats subject
team_idNoOptional numeric team id to filter player stats
positionNoOptional client-side player position filter
league_idYesNumeric FotMob league id
season_idNoNumeric season id from /fotmob/stats-categories; defaults to the newest season

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the burden and does add useful behavior: stat id variability, team_id restricting player stats, and position filtering happening client-side. It does not disclose return format, pagination, or error behavior, so it is only partially 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?

Three sentences, each with a distinct job: what the tool returns, the stat-id dependency, and optional parameter behavior. No filler.

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

Completeness3/5

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

For a 6-parameter tool with no output schema, the description covers the core call pattern and optional filters. However, it does not explain where league_id comes from or what the ranked response structure looks like, leaving some ambiguity for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds real value by explaining that stat ids come from /fotmob/stats-categories and vary, that team_id only affects player stats, and that position filtering is client-side. This goes beyond the schema's property descriptions.

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?

The description opens with 'FotMob league player or team statistics' and says it 'returns ranked player or team statistics for a stat id discovered from /fotmob/stats-categories,' giving a clear verb and resource. It distinguishes itself from the stats-categories discovery tool, though it does not explicitly name sibling tools like fotmob_player_stats.

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?

It tells the agent that stat ids must first be discovered from /fotmob/stats-categories and warns that accepted ids vary by league, season, and type. This implies a prerequisite but does not explicitly state when to choose this tool over fotmob_player_stats, fotmob_table, or other FotMob tools.

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