Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

sofascore_scheduled_events

SofaScore events scheduled in a category on a date. Returns the events (matches) in one category, such as a country, that start on a UTC date, ordered by start time.

Instructions

SofaScore events scheduled in a category on a date. Returns the events (matches) in one category, such as a country, that start on a UTC date, ordered by start time. Get the category id from the categories endpoint (or category_id from scheduled-tournaments). date must be a real calendar date written YYYY-MM-DD and is a UTC day; to cover a local day in another timezone, request the neighbouring dates and filter on start_timestamp. An empty events list is a valid response when the category has no fixtures that day. Returns 404 for an unknown category id.

Input Schema

NameRequiredDescriptionDefault
dateYesUTC calendar date, YYYY-MM-DD
category_idYesNumeric SofaScore category id from the categories endpoint

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.12

TDQS

A4.3/5.0
Behavior4/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 well: it discloses ordering by start time, that an empty events list is a valid response, that unknown category ids return 404, and that the date is interpreted as a UTC day. It does not describe the shape of individual event objects, but the behavioral profile is solidly covered.

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 core verb+resource, then supporting detail in a logical order (id sourcing, date semantics, empty-list note, 404). It is somewhat dense in the middle but every sentence adds usable information; no filler.

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?

For a two-parameter lookup with no output schema, the description supplies the key return semantics (ordered events, empty-list validity, 404 on bad id) that an agent needs. It is nearly complete, with only per-event field structure left unspecified.

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 baseline is 3, but the description adds real meaning beyond the schema: the date must be a 'real calendar date' in YYYY-MM-DD interpreted as UTC, plus where to obtain category_id. The timezone guidance ties directly to how the parameters are used correctly.

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: events scheduled in a category on a UTC date, returned ordered by start time. This is precise enough to distinguish it from siblings like sofascore_scheduled_tournaments, sofascore_live_events, and sofascore_category_tournaments without opening any 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?

Gives clear operational context: where to source the category id (categories endpoint or scheduled-tournaments), how to handle local timezones (request neighbouring dates and filter on start_timestamp), and the date format. It lacks an explicit 'use this instead of X when...' exclusion against the other events-listing siblings, so it stops just short of a 5.

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