Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fotmob_fifa_ranking_periods

List FIFA ranking periods available on FotMob for men's or women's rankings, returning each periodId and date label to query the rankings endpoint.

Instructions

FotMob FIFA ranking period directory. Lists the FIFA ranking periods FotMob currently offers for the required gender (men or women). Each period has a periodId and a periodName date label. Pass a periodId to the FotMob FIFA rankings endpoint; the ids change over time and are not a fixed set.

Input Schema

NameRequiredDescriptionDefault
genderYesRanking gender

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.6

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose meaningful behavior: the returned ids 'change over time and are not a fixed set,' which warns the agent not to cache or hardcode them. It also describes the return fields (`periodId`, `periodName`). It stops short of stating read-only/safety characteristics or whether the directory can be empty.

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 tight sentences, front-loaded with what the tool is and immediately followed by the required parameter and the downstream use of the returned id. No padding.

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?

With no output schema, the description usefully names the returned fields and explains their volatility. For a one-parameter directory lookup this is largely complete, though it omits anything about ordering, volume, or failure cases.

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%, so the single `gender` parameter and its `men`/`women` enum are already documented. The description restates the enum values and the requiredness without adding syntax or format detail beyond the schema, so 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: it 'Lists the FIFA ranking periods FotMob currently offers.' It also implicitly distinguishes itself from the sibling `fotmob_fifa_rankings` by positioning itself as the period directory that feeds that endpoint.

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?

Clearly explains the workflow: call this to obtain a `periodId`, then 'Pass a `periodId` to the FotMob FIFA rankings endpoint.' The dependency on the rankings call is explicit, though it never names the sibling tool directly or states when this tool is not needed.

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