Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

sofascore_team_rankings

Read-only

Returns every ranking a SofaScore team or tennis player appears in (ATP or WTA, live ranking, UTR rating, or UEFA club coefficient by year) with position, points, previous and best position, and the ranking type id that sofascore_rankings accepts. Use it for one subject's standing; not found means the id is in no ranking.

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": {
      "id": "<id>"
    },
    "name": "sofascore_team_rankings"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesRequired. Numeric SofaScore team id, e.g. 2817.

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. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds real behavioral context beyond them: the returned fields, the fact that the ranking type id feeds sofascore_rankings, and the meaning of a not-found result.

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?

Two dense sentences, front-loaded with the resource and scope before the usage note. Every clause carries information, though the parenthetical ranking list is long enough to slow the opening slightly.

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?

With an output schema present, the description need not explain return format, yet it still summarizes the key fields and the cross-tool handoff to sofascore_rankings. Nothing an agent needs to call this correctly 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% and the single id is well documented in the schema. The description adds that the id may be a team or a tennis player and ties the ranking set to that subject, which is slightly more than the schema's 'SofaScore team id' wording, though it borders on a minor mismatch.

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 ('Returns') and resource ('every ranking a SofaScore team or tennis player appears in'), and enumerates the ranking families (ATP/WTA, live ranking, UTR, UEFA club coefficient). It is clearly distinguishable from the sibling sofascore_rankings, which it explicitly cross-references as the consumer of the returned ranking type id.

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?

'Use it for one subject's standing' gives clear usage context, and 'not found means the id is in no ranking' sets a useful expectation for empty results. However, it does not explicitly say when to prefer sofascore_rankings instead, so the routing logic is only implied.

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