Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fotmob_fifa_rankings

Returns national-team FIFA rankings, points, and rank changes for one period by gender. Use a period ID from the ranking periods endpoint.

Instructions

FotMob FIFA national-team rankings. Returns ranked national-team points and rank changes for one period. Discover valid periodId values for the selected gender from /fotmob/fifa-ranking-periods.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
genderYesRanking gender
period_idYesPeriod id returned for this gender by /fotmob/fifa-ranking-periods

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.6

TDQS

A4/5.0
Behavior3/5

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

There are no annotations, so the description carries the behavioral-disclosure burden. It states the return contents (ranked points and rank changes for one period), which is useful, but it does not mention read-only status, pagination, authentication, or error behavior.

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?

The description is three short sentences and front-loads the tool's identity and output before the prerequisite. Every sentence serves a purpose with no redundant or vague language.

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?

For a simple two-parameter read tool with no output schema and no annotations, the description is nearly complete: it explains what is returned and how to obtain a valid period. It could be slightly richer about return shape or pagination, but it is sufficient for correct invocation.

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 both parameters are already documented in the input schema. The description reinforces the dependency between gender and period_id and points to the discovery endpoint, but adds no syntax or format detail beyond the schema.

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 states a specific verb and resource: it returns FotMob FIFA national-team rankings, with ranked points and rank changes for one period. It also implicitly distinguishes itself from the sibling fotmob_fifa_ranking_periods tool by pointing to that endpoint for period discovery.

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?

It clearly explains the prerequisite: periodId must be discovered via /fotmob/fifa-ranking-periods for the selected gender. It does not give explicit when-not-to-use guidance, but the context is clear for a single-purpose ranking retrieval tool.

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