Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sofascore_team_events

Fetch a SofaScore team's upcoming or recent fixtures by team ID and direction; paginate results and return an empty events list when no fixture exists.

Instructions

SofaScore team fixtures. Returns a page of a team's upcoming or recent fixtures. The direction enum accepts next and last. An empty events list is a valid response when there is no fixture on that page.

Input Schema

NameRequiredDescriptionDefault
idYesNumeric SofaScore team id
pageNoZero-based page number
directionYesFixture direction

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / direction / enum
      Added value: +[
+  "next",
+  "last"
+]
  2. Addedv1.5.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It helpfully discloses pagination ('a page'), the valid direction values, and that an empty `events` list is a legitimate result, but it omits auth/permission needs and what fields the fixtures contain.

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?

Three tight sentences, purpose front-loaded, no filler. The direction enum restatement is mildly redundant against the schema, keeping it just short of 5.

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 simple 3-param, no-output-schema fixtures tool, the description covers scope, pagination, enum values, and the empty-result case. It could mention what a fixture entry contains, but nothing essential for calling 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 coverage is 100%, so the schema already documents id, page, and direction. The description re-states the direction enum and the empty-list case rather than adding syntax or format meaning, so the baseline 3 applies.

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?

States a specific verb+resource: returns a team's upcoming or recent fixtures. Clear enough to distinguish from a generic team tool, but it never contrasts with close siblings like sofascore_team_near_events or sofascore_event, so the agent must infer which fixture endpoint to pick.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the direction enum and pagination note, but there is no explicit when-to-use vs alternatives guidance or precondition (e.g., 'use this for a fixed team id, not for search'). The agent gets context but no routing rules.

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