Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

sofascore_tournament_winners

Read-only

Returns one page of 10 past winners of a SofaScore competition, newest first, with the year, season id and winning team or player. Pass the zero-based page and follow has_next_page for older seasons; a page past the last one returns not found.

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_tournament_winners"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesRequired. Numeric SofaScore unique-tournament (competition) id, e.g. 17 for the Premier League.
pageNoOptional. Zero-based page number, 10 winners per page, newest first. Defaults to 0. Follow has_next_page for more.

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.7/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true and openWorldHint=true. The description adds pagination semantics (10 per page, newest first) and the not-found behavior for out-of-range pages, which goes beyond the annotations. It doesn't mention auth or rate limits, but for a read-only lookup that may not be critical.

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?

Two tight sentences that front-load the operation, scope, and pagination rule. No wasted words; every sentence earns its place.

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 needn't explain return values, and it covers the key operational behaviors: pagination, ordering, and not-found handling. For a simple paginated read tool, this is complete.

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 schema fully documents 'id' and 'page'. The description reinforces that 'page' is zero-based with 10 winners per page and that has_next_page should be followed, adding slight clarification beyond the schema, though it does not introduce new syntax or constraints.

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 one page of 10 past winners of a SofaScore competition, newest first.' An agent can distinguish this from siblings like sofascore_tournament_teams or sofascore_tournament_info without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly instructs 'Pass the zero-based page and follow has_next_page for older seasons' and warns 'a page past the last one returns not found.' This gives clear pagination context and error expectation without needing a sibling alternative.

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