Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sofascore_standings

Fetch a league table for a competition season. Specify total, home, or away standings using competition id and season id.

Instructions

SofaScore standings. Returns a league table for a competition season. The type enum accepts total, home, and away. Get id from search and season from tournament-seasons.

Input Schema

NameRequiredDescriptionDefault
idYesNumeric SofaScore unique-tournament (competition) id
typeYesStandings variant
seasonYesNumeric SofaScore season id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / type / enum
      Added value: +[
+  "total",
+  "home",
+  "away"
+]
  2. Addedv1.5.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations or output schema, so the description carries the full burden. It discloses that the output is a league table and that the variant differs by type, and it implicitly implies a read operation. But it doesn't describe the table contents, sort order, what season scope means, or any rate/auth characteristics.

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 short sentences, purpose front-loaded, enum noted for the required third parameter. No filler. Slightly formulaic ('SofaScore standings' restates the name) but efficient overall.

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 3-required-param read tool with no annotations or output schema, the description covers what an agent needs to call it: purpose, enum behavior, and referral to where ids/seasons come from. Return structure is only minimally described, but that is a minor gap.

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% (baseline 3), and the description still adds real value beyond the schema by stating the source of `id` (search) and `season` (tournament-seasons) and by restating the type enum variants. The sourcing hints plus enum reinforcement push it above the baseline.

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+resource: 'Returns a league table for a competition season.' An agent can tell this returns standings rather than events, stats, or season lists. It does not explicitly name or contrast with siblings like sofascore_tournament_info or flashscore_tournament_standings, so not a 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 a concrete workflow: 'Get `id` from search and `season` from tournament-seasons.' This tells the agent how to obtain required inputs and implies when it applies (once you have a competition and season). It stops short of naming when NOT to use this tool or naming alternative standings tools.

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