Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sofascore_venue_events

SofaScore matches at a venue. Returns one page (up to 30) of the matches played (direction last, newest page first) or scheduled (next) at a venue, as match summaries.

Instructions

SofaScore matches at a venue. Returns one page (up to 30) of the matches played (direction last, newest page first) or scheduled (next) at a venue, as match summaries. Without tournament and season it lists every match at the venue, optionally narrowed by sport (all, or any key listed in the venue's sports, such as football, rugby, basketball, mma); with both it lists that competition season's matches at the venue and sport must be omitted. Hidden venues (see venue) have no venue-wide list and answer 404 without tournament and season. A direction with no matches, a sport the venue never hosted and a page past the last one also answer 404; follow has_next_page.

Input Schema

NameRequiredDescriptionDefault
idYesNumeric SofaScore venue id
pageNoZero-based page number. Defaults to 0
sportNoSport filter for the venue-wide list. Defaults to all
seasonNoNumeric season id; with tournament, lists that competition season's matches at the venue
directionYesUpcoming matches or finished matches
tournamentNoNumeric unique-tournament id; with season, lists that competition season's matches at the venue

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.12

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it discloses pagination size (30), ordering (newest page first), hidden-venue behavior, and the three distinct 404 conditions (empty direction, unhosted sport, page past last). This is genuinely useful behavior an agent cannot infer from the schema.

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-loaded with the purpose and page/return shape before drilling into the filter matrix and error cases. Dense but nearly every clause conveys a distinct constraint; slightly long, but not padded.

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?

No output schema exists, yet the description names the return unit (match summaries), the page size, and the pagination signal (has_next_page). Combined with documented filter interactions and error conditions, an agent has everything needed to call and iterate correctly.

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 baseline is 3, but the description adds real semantics beyond the schema: the sport enum must be omitted when tournament+season are given, sport values must come from the venue's listed sports, and direction selects newest-first vs upcoming. These constraints go beyond the field descriptions.

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?

The description states a specific verb and resource (matches played/scheduled at a venue) plus the return shape (one page, up to 30, as match summaries). It is clearly distinguishable from sofascore_venue (venue info) and sofascore_team_events, though it never names a sibling to route against.

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?

Explicit conditional guidance: without tournament+season it lists all venue matches optionally narrowed by sport; with both it lists that competition season and sport must be omitted. It also covers the 404 edge cases and tells the agent to follow has_next_page.

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