Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

sofascore_rankings

Read-only

Returns one SofaScore ranking list with rank, previous rank, points and the ranked team, player or competition, plus the last update time. Pass a type id from sofascore_ranking_types, for example 5 for the ATP men's singles ranking; optional limit returns only the first rows of long lists. MMA division rankings use rank 0 for the champion.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "type": "<type>"
    },
    "name": "sofascore_rankings"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesRequired. Ranking id from the ranking-types endpoint, e.g. 5 for the ATP men's singles ranking.
limitNoOptional. Return only the first N rows, 1 to 500. Omit to return every row.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds genuinely new behavioral detail: the shape of a row, that limit truncates long lists, and the non-obvious rule that MMA division rankings use rank 0 for the champion. It does not discuss pagination, refresh cadence, or failure modes, but the annotation bar is met.

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, no filler, with the core purpose and return shape front-loaded before the parameter guidance and the special case. Every sentence carries actionable information.

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?

For a two-parameter read tool with an output schema, the description covers what an agent needs: what comes back, where the required id comes from, how to trim results, and one domain gotcha. Nothing material is missing.

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 the baseline is 3, but the description goes beyond the schema by giving a concrete example id (5 = ATP men's singles) and the rank-0 champion convention that affects interpretation of results. The limit parameter's 'first rows of long lists' framing also adds intent beyond 'return only the first N rows'.

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 ('Returns one SofaScore ranking list') and enumerates the returned fields (rank, previous rank, points, ranked entity, last update time). It also points at the sibling tool that supplies the required id (sofascore_ranking_types), so an agent can distinguish it from the rankings/standings siblings without opening a schema.

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 clear context: supply a type id from sofascore_ranking_types, with a concrete example (5 = ATP men's singles), and explains the optional limit for long lists. It stops short of any explicit when-not-to-use guidance or comparison against other ranking sources, so it is clear but not exhaustive.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources