Crawlora MCP

sofascore_venue

Read-only

Returns one SofaScore venue (stadium or arena): name, capacity, city, country, coordinates, home teams, venue-wide match totals and a per-sport match record. Hidden venues such as NBA arenas have no venue-wide match list; use sofascore_venue_events with a competition season for them. Requires a venue id from sofascore_search_typed or sofascore_tournament_venues.

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

Input Schema

Name	Required	Description	Default
`id`	Yes	Required. Numeric SofaScore venue id, e.g. 624 for the Emirates Stadium. Find ids with sofascore_search_typed (type venues) or sofascore_tournament_venues.

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.

AddedOct 7, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered by structured data. The description adds a genuinely useful behavioral caveat that annotations cannot express: certain venues (e.g. NBA arenas) lack venue-wide match data, which would otherwise look like an empty result. It stops short of coverage/rate-limit detail, so not a 5.

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?

Three sentences, each doing distinct work: what it returns, the hidden-venue exception with its alternative, and the id prerequisite. The payload description is front-loaded and there is no filler.

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?

An output schema exists, so return-value explanation is unnecessary, yet the description still summarizes the returned content and adds the edge-case routing rule. 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.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only one parameter with 100% schema description coverage, so the schema already carries the semantics (numeric venue id, example 624, sources for ids). The description repeats the id sourcing rather than adding syntax or format meaning beyond it. Baseline 3 is correct.

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 one SofaScore venue (stadium or arena)') and enumerates the returned fields: name, capacity, city, country, coordinates, home teams, match totals, per-sport record. It also explicitly distinguishes itself from sofascore_venue_events, so an agent can route without opening either 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?

Gives both the when-not ('Hidden venues such as NBA arenas have no venue-wide match list') and the alternative plus its required input ('use sofascore_venue_events with a competition season for them'). It also states the prerequisite for the id parameter, so the full call path is documented.

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?