Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

sofascore_tournament_teams

Read-only

Returns every team (or player, in tennis and other individual sports) entered in a SofaScore competition season, with id, name, code, country, type and the ranking of players. Use the ids with sofascore_team and the team filter of sofascore_tournament_player_statistics; requires a competition id and a season id from sofascore_tournament_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>"
    },
    "name": "sofascore_tournament_teams"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesRequired. Numeric SofaScore unique-tournament (competition) id, e.g. 17 for the Premier League.
seasonYesRequired. Numeric SofaScore season id (from tournament-seasons), e.g. 96668.

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

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the enumeration scope ('every team... entered in a season'), but says nothing about pagination, result size, or freshness/live-vs-final data, leaving the behavioral picture thin beyond what the annotations provide.

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 sentences, front-loaded with the purpose and zero filler. The second sentence packs three clauses (downstream use, two tools, prerequisite source) and is slightly dense, but every clause earns its place.

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 only two well-documented required params, an output schema covering the return shape, and annotations covering safety, the description supplies everything an agent needs to call it correctly. Only marginal gaps remain (pagination/max result behavior for a potentially large squad list).

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 description coverage is 100% with examples (17 for Premier League, 96668), so the schema carries the parameter burden. The description still adds provenance by stating both ids come from sofascore_tournament_seasons, which is meaning beyond the schema itself.

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 every team (or player, in tennis and other individual sports) entered in a SofaScore competition season.' It enumerates returned fields (id, name, code, country, type, ranking) and immediately distinguishes its scope from generic team tools, so an agent can tell what it produces 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 Guidelines4/5

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

It names downstream consumers (sofascore_team, the team filter of sofascore_tournament_player_statistics) and the prerequisite chain (competition id + season id from sofascore_tournament_seasons). That is strong routing, though it frames guidance as what to do with the output rather than when to prefer this tool over them.

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