Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sofascore_event_votes

Retrieve SofaScore match community vote tallies for result, both teams to score, first scorer, and who should have won, or 404 when no votes exist.

Instructions

SofaScore event votes. Returns a match's community vote tallies: the match result vote (match_result with home, away, total and draw, where draw is absent for two-way sports such as basketball and tennis), both teams to score, which team scores first and who should have won (when SofaScore has opened that vote). A block that holds no votes is omitted. Returns 404 when SofaScore has no votes for the match.

Input Schema

NameRequiredDescriptionDefault
idYesNumeric SofaScore event (match) id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.12

TDQS

A4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it does disclose return structure, the omission of empty vote blocks, and the explicit 404-on-no-votes error condition. It omits auth requirements or rate limits, but for a simple read endpoint the disclosed edge-case behavior is strong.

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 front-loaded with the core purpose and then adds necessary detail on vote structure and error behavior. It is somewhat dense in the enumeration, but every clause carries useful information and nothing is wasted.

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 no output schema and no annotations, the description fully compensates by describing the returned vote fields, how two-way sports differ, and the 404 behavior. For a one-parameter read tool this is complete enough for an agent to call it correctly.

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% and the single `id` parameter is already documented as the numeric SofaScore event id, so the description adds no parameter-level meaning beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 match's community vote tallies) and enumerates the vote categories it covers (match result, both teams to score, first scorer, who should have won). This is specific enough that an agent can distinguish it from siblings like sofascore_event_comments or sofascore_event_statistics 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 Guidelines3/5

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

The description explains output-shape conditions (empty blocks omitted, 404 when no votes, draw absent for two-way sports), which implicitly tells the agent when the tool will and won't yield data. However, it never states when to prefer this tool over another SofaScore vote/comment/stat endpoint, so selection guidance remains implied rather than explicit.

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