Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sofascore_team_events

Fetch a team's upcoming or recent SofaScore fixtures by ID and direction. Get paginated JSON results for match schedules.

Instructions

SofaScore team fixtures. Returns a page of a team's upcoming or recent fixtures from SofaScore's credential-free public JSON. 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

TableJSON 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.8/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. It usefully discloses that the API is credential-free, that direction uses next/last, and that an empty events list is a valid response. It does not cover rate limits, error behavior, or the event object shape, but covers the most important behavioral traits.

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?

The description is short, front-loaded, and easy to scan. The opening phrase 'SofaScore team fixtures' is slightly redundant with the description's second sentence, but the overall structure is efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no output schema and no annotations, the description provides enough to invoke it correctly: required id, direction semantics, and a valid empty response. However, it does not describe the event object shape, page defaulting, or how this tool relates to nearby SofaScore tools.

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 adds little beyond restating that direction accepts next/last and noting the empty-response case, which is output-related rather than parameter-specific.

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?

The description clearly states what the tool does: it returns a page of a team's upcoming or recent fixtures from SofaScore. The phrase 'team fixtures' distinguishes it from sibling tools like sofascore_round_events or sofascore_live_events.

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?

The description implies when to use this tool (when a team's fixtures are needed) but does not explicitly name alternatives or state conditions for choosing between this and related SofaScore tools. Usage is clear but not prescriptive.

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