Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sofascore_rankings

SofaScore rankings. Returns one SofaScore ranking list: the rank, previous rank, points and the ranked team, player or competition, plus when the list was last updated.

Instructions

SofaScore rankings. Returns one SofaScore ranking list: the rank, previous rank, points and the ranked team, player or competition, plus when the list was last updated. Choose the type id from sofascore-ranking-types, for example 5 for the ATP men's singles ranking or 2 for the FIFA men's national team ranking. Optional limit returns only the first rows of long lists (tennis lists hold 500 rows). MMA division rankings use rank 0 for the reigning champion.

Input Schema

NameRequiredDescriptionDefault
typeYesRanking id from sofascore-ranking-types
limitNoReturn only the first N rows, 1 to 500. Omit to return every row

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.12

TDQS

A4/5.0
Behavior4/5

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

With no annotations the description carries the full burden, and it does disclose return contents plus real edge cases: tennis lists hold 500 rows, limit truncates to first N, and MMA division rankings use rank 0 for the reigning champion. It omits auth/rate-limit behavior, so not a 5.

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?

Front-loaded with the core statement ('SofaScore rankings. Returns one...') and each following sentence adds distinct information (fields, type routing, limit, MMA edge case). Efficient, though slightly dense rather than maximally tight.

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?

No output schema exists, so the description must cover return values, which it does by listing the returned fields. Both parameters are addressed with examples and behavior. Adequate for a two-param lookup, minor gap only around freshness/caching.

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 genuine meaning beyond the schema: example id values for type (5 for ATP, 2 for FIFA) and context for limit (first rows of long lists, sizes up to 500). This is more than the enum/description already provides.

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 ('Returns one SofaScore ranking list') and enumerates the exact fields returned: rank, previous rank, points, the ranked entity, and last-updated time. It routes the agent to the sofascore-ranking-types helper for the id. It does not explicitly distinguish itself from adjacent siblings like sofascore_team_rankings, so not a full 5.

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 concrete usage guidance: 'Choose the type id from sofascore-ranking-types' with worked examples (5=ATP singles, 2=FIFA national teams), and explains when to use limit. It lacks any when-not-to-use or explicit alternative for other ranking tools, so short of the top band.

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