Crawlora MCP

sofascore_team_events

Read-only

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. id: Required. Numeric SofaScore team id, e.g. 2817. Use fotmob_team_fixtures to retrieve fotMob paginated team fixtures.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>",
      "direction": "<direction>"
    },
    "name": "sofascore_team_events"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Required. Numeric SofaScore team id, e.g. 2817.
`page`	No	Optional. Zero-based page number. Defaults to 0 (most recent page).
`direction`	Yes	Required. One of next, last.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds real value: it notes the source is credential-free public JSON, that results are paginated, and that an empty events list is a valid (not error) response, which prevents misreading empty results.

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 purpose and reasonably compact, though the 'id: Required. Numeric SofaScore team id, e.g. 2817.' sentence duplicates the schema verbatim and is mildly redundant.

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 an output schema present, return values need not be explained. The description covers pagination, the valid-empty-list case, and source provenance, leaving little an agent needs to call it correctly beyond the covered fields.

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 description coverage is 100%, so the schema already documents id, page, and direction. The description largely restates the required id and the direction values, adding no syntax or format detail beyond the schema, so baseline 3 applies.

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 ('Returns') and resource (a team's upcoming or recent fixtures), and the direction enum (next/last) lets an agent distinguish this from related fixture tools. It is unambiguous about what the tool retrieves.

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?

It offers one routing hint ('Use fotmob_team_fixtures to retrieve fotMob paginated team fixtures'), but this points at a different provider rather than explaining when to prefer this tool over same-family siblings like sofascore_team_near_events. Usage is implied by the direction enum but not fully guided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?