Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sofascore_scheduled_tournaments

SofaScore tournaments scheduled on a date. Returns one page of the tournaments that have fixtures on a UTC date for a sport, each with the number of events starting that UTC day.

Instructions

SofaScore tournaments scheduled on a date. Returns one page of the tournaments that have fixtures on a UTC date for a sport, each with the number of events starting that UTC day. This lists competitions, not matches: use scheduled-events with a tournament's category_id for the matches, or its unique_tournament_id with the tournament-seasons and round endpoints. date must be a real calendar date written YYYY-MM-DD. Pages are one-based; follow has_next_page. The sport enum accepts american-football, aussie-rules, badminton, bandy, baseball, basketball, beach-volley, cricket, darts, esports, floorball, football, futsal, handball, ice-hockey, mma, minifootball, padel, rugby, snooker, table-tennis, tennis, volleyball, and waterpolo. An empty tournaments list is a valid response for a date with no fixtures or a page past the last one.

Input Schema

NameRequiredDescriptionDefault
dateYesUTC calendar date, YYYY-MM-DD
pageNoOne-based page number; defaults to 1
sportYesSport key

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.12

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are present, so the description carries the full burden, and it does well: discloses one-page return semantics, one-based paging, following `has_next_page`, and that an empty `tournaments` list is a valid response. It omits any explicit mention of auth, rate limits, or item shape beyond the event count, so not a full 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well front-loaded, with the key routing sentence first. However, it spends a large block re-listing all 24 sport enum values that the schema already enumerates, which is redundant padding rather than added meaning.

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 no output schema, the description steps up by describing the return ('one page of the tournaments ... each with the number of events starting that UTC day') and the valid-empty-list case, plus sibling routing. Complete enough to invoke correctly, though it could say more about result shape.

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 coverage is 100%, so the schema already documents the date format, one-based page default, and the full enum. The description largely restates these ('date must be a real calendar date written YYYY-MM-DD', 'Pages are one-based'). Baseline 3 when the schema does the heavy lifting, with only the 'real calendar date' nuance adding marginal value.

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 ('SofaScore tournaments scheduled on a date') and immediately clarifies scope: 'This lists competitions, not matches.' An agent can tell it apart from scheduled-events and related endpoints 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?

Explicitly routes the agent: use scheduled-events with a tournament's `category_id` for matches, or `unique_tournament_id` with tournament-seasons and round endpoints. It also states the date format constraint and pagination-following rule, leaving little to inference.

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