Crawlora MCP

sofascore_standings

Read-only

Returns a league table for a competition season from SofaScore's credential-free public JSON. The type enum accepts total, home, and away. Get id from search and season from tournament-seasons. Use sofascore_tournament_seasons to retrieve sofaScore competition seasons.

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>",
      "season": "<season>",
      "type": "<type>"
    },
    "name": "sofascore_standings"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Required. Numeric SofaScore unique-tournament (competition) id, e.g. 17 for the Premier League.
`type`	Yes	Required. One of total, home, away.
`season`	Yes	Required. Numeric SofaScore season id (from tournament-seasons), e.g. 76986.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A4.3/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 that the data comes from credential-free public JSON, which tells the agent no authentication is required. It stops short of describing rate limits or pagination, but the added auth context is genuinely useful.

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?

Three sentences, front-loaded with the core purpose. Slight redundancy between 'tournament-seasons' and 'sofascore_tournament_seasons,' but nothing is wasted and the prerequisites follow logically.

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 an output schema present, the description needn't explain return values, and it covers purpose, prerequisite sourcing, and the enum. Nothing an agent needs to call it 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%, so baseline is 3. The description adds procedural meaning beyond the schema by explaining where id and season originate (search, tournament-seasons), though the type enum values largely restate the schema's 'One of total, home, away'.

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+resource+scope: 'returns a league table for a competition season.' An agent can tell it apart from siblings like sofascore_tournament_standings and sofascore_stage_standings, and it names its data source.

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 prerequisites for two of three params ('get id from search and season from tournament-seasons') and routes to sofascore_tournament_seasons. No explicit when-not condition, but the sourcing guidance is more than most siblings provide.

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

All Crawlora MCP tools Inspect

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

Need Help?