Crawlora MCP

sofascore_event_shotmap

Read-only

Returns every shot in a football or ice hockey match for one SofaScore event id. Football shots carry shooter, side, outcome, situation, body part, expected goals (xG, xGOT), minute and pitch plus goal-mouth coordinates; hockey shots carry shooter, team, outcome (made, saved, missed, blocked), strength (even, powerplay, shorthanded), period clock, rink coordinates and xg. Use it for chance-quality analysis beyond sofascore_event_statistics totals. An empty list is valid for a live match with no shots yet; a not-found error means no shot map exists, including basketball.

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_shotmap"
  }
}

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.

AddedOct 7, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description goes further by disclosing outcome semantics: an empty list is valid for a live match with no shots yet, and a not-found error means no shot map exists (including basketball) — genuinely useful failure-mode context that annotations cannot convey.

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 purpose, then usage, then edge-case behavior, so the most decision-relevant content comes first. The middle sentence enumerating every returned field is long and partly overlaps the output schema, slightly diluting the otherwise tight structure.

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?

With an output schema present, the description needn't explain return values, yet it still covers schema, usage routing, empty-result validity, and error meaning. Nothing an agent needs in order to call 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?

Only one parameter and schema coverage is 100%, so the baseline is 3. The description restates that the call targets 'one SofaScore event id' but adds no format or syntax detail beyond what the schema already provides ('Numeric SofaScore event (match) id, e.g. 14025013').

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 precise verb and resource ('Returns every shot'), scopes it to football/ice hockey matches keyed by one SofaScore event id, and explicitly distinguishes itself from the sibling sofascore_event_statistics. An agent can identify the tool without opening the 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 it for chance-quality analysis beyond sofascore_event_statistics totals,' naming the alternative and the condition that selects it. It also bounds applicability by noting basketball has no shot map and that an empty list is legitimate for live matches, giving both when-to-use and when-not signals.

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?