Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sofascore_tournament_venues

SofaScore venues of a competition season. Returns every venue used by a competition season with id, name, capacity, city, state (US), coordinates and the hidden flag. Use the venue ids with venue and venue-events.

Instructions

SofaScore venues of a competition season. Returns every venue used by a competition season with id, name, capacity, city, state (US), coordinates and the hidden flag. Use the venue ids with venue and venue-events. A season id that does not belong to the competition answers 404. Get id from search and season from tournament-seasons.

Input Schema

NameRequiredDescriptionDefault
idYesNumeric SofaScore unique-tournament (competition) id
seasonYesNumeric SofaScore season id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.12

TDQS

A4.4/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 burden, and it does disclose meaningful behavior: the exact returned fields (including the `hidden` flag) and the 404 error when a season id does not belong to the competition. It doesn't mention rate limits or pagination, but the edge-case/error disclosure is solid for a read tool.

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, followed by return fields, then usage and error behavior. Four sentences, each functional with no filler, though the flow of return-fields-before-usage is slightly less ideal than leading with the action.

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, the description enumerates the returned fields (id, name, capacity, city, state, coordinates, hidden) and closes the loop on inputs and 404 behavior. An agent has everything needed to call and interpret this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% so the baseline is 3, but the description adds real meaning beyond the schema by specifying provenance for each param: `id` comes from search and `season` from tournament-seasons. This resolves the ambiguity of which ids are expected without the agent needing to guess.

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+resource: it returns every venue used by a competition season, and it explicitly names the scope (competition season). It distinguishes itself from the sibling sofascore_venue and sofascore_venue_events by positioning itself as the season-wide venue list that feeds those tools.

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 explicit workflow guidance: 'Use the venue ids with venue and venue-events,' and states where each input comes from ('Get id from search and season from tournament-seasons'). It clarifies the follow-on tools but stops short of stating when NOT to use this tool versus those siblings.

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