Crawlora MCP

sofascore_venue_events

Read-only

Returns one page of up to 30 matches played (direction last) or scheduled (next) at a SofaScore venue, as match summaries with teams, status and score. Narrow with sport (all or a sport key), or pass tournament and season together for one competition season; hidden venues only list matches per competition season. Follow has_next_page for more pages.

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>",
      "direction": "<direction>"
    },
    "name": "sofascore_venue_events"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Required. Numeric SofaScore venue id, e.g. 624 for the Emirates Stadium.
`page`	No	Optional. Zero-based page number, up to 30 matches per page. Defaults to 0. Follow has_next_page for more.
`sport`	No	Optional. One of all or a sport key from the venue's sport_statistics (football, basketball, rugby, mma, and so on). Defaults to all. Cannot be combined with tournament and season.
`season`	No	Optional. Numeric season id; with tournament, restricts the matches to that competition season. Must be given together with tournament.
`direction`	Yes	Required. One of next (upcoming matches), last (finished matches, newest page first).
`tournament`	No	Optional. Numeric unique-tournament (competition) id; with season, restricts the matches to that competition season. Must be given together with season.

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.2/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 genuinely useful behavior: page size cap of 30, the has_next_page pagination signal, and the hidden-venue restriction that forces per-competition-season listing. This goes beyond what the annotations state, though it doesn't discuss auth or latency 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?

Front-loads what is returned and the page size, then layers the filtering rules and pagination follow-up. Dense but every clause carries signal; the sport/tournament clause is slightly compressed but readable.

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 values need no elaboration, and the description still covers pagination, filtering combinations, and the hidden-venue edge case. Nothing an agent needs to invoke it 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?

Schema description coverage is 100%, so the schema already documents all six parameters, including direction values and the sport/tournament/season constraints. The description largely restates these, adding only the minor semantic mapping of last=played and next=scheduled. Baseline 3 is appropriate.

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 (returns matches at a SofaScore venue), the scope (one page, up to 30), and the two modes (played via direction=last, scheduled via next). It also names the fields returned (teams, status, score), letting an agent distinguish it from siblings like sofascore_team_events or sofascore_season_events.

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?

Explains the two selection modes via direction, how to narrow by sport, and that tournament+season must be passed together for a single competition season, plus the hidden-venue constraint. It gives clear context but does not explicitly route the agent to an alternative tool (e.g. team/season events) when those would be more appropriate.

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?