Crawlora MCP

sofascore_event_graph

Read-only

Returns a match's momentum graph as minute and value points (positive favours the home side) plus period lengths, for one SofaScore event id of a football, ice hockey or basketball match. Use it to see which side was on top during the game. An empty list is valid for a live match that has just started; a not-found error means no graph exists, including tennis and baseball.

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>"
    },
    "name": "sofascore_event_graph"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Required. Numeric SofaScore event (match) id, e.g. 14025013.

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 7, 2026

TDQS

A4.3/5.0

Behavior4/5

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

The annotations cover the safety profile (readOnly, openWorld), and the description adds genuinely useful behavior beyond that: sign convention (positive favours home side), the meaning of an empty result, and the semantics of a not-found error including which sports are unsupported. Minor gap only in not mentioning caching or latency characteristics.

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

Conciseness5/5

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

Three sentences, all earning their place: payload first, purpose second, edge cases third. Zero filler and the most important information (what is returned) is front-loaded.

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

Completeness5/5

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

For a single-parameter read tool with an output schema present, the description covers everything the agent needs: return shape, sign convention, sport scope, and the two non-obvious response states (empty vs not-found). Nothing essential 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 description coverage is 100% with a single required 'id' that is already fully documented in the schema, so the baseline is 3. The description restates 'one SofaScore event id' but adds no format or constraint detail beyond what the schema already says.

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), resource (match's momentum graph), and the exact payload shape (minute and value points plus period lengths). It also scopes the supported sports, so an agent can tell it apart from the many other sofascore_event_* siblings without opening a 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 a clear use case ('Use it to see which side was on top during the game') and draws the edge-case boundaries: empty list is valid for a just-started live match, not-found means no graph exists for tennis/baseball. It does not name a specific sibling alternative, so it stops 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.

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.