Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

sofascore_venue

Instructions

SofaScore venue. Returns one venue (stadium or arena): name, capacity, city, country, coordinates, its home teams, the venue-wide match totals (matches, goals, home and away win shares, and for football cards and corners per game) and a per-sport record in sports, most matches first. hidden venues, such as NBA arenas, have no venue-wide match list in venue-events and are listed per competition season instead. An unknown venue id answers 404. Get id from search-typed with type venues, from tournament-venues or from an event's venue.

Input Schema

Name	Required	Description	Default
`id`	Yes	Numeric SofaScore venue id

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.12Oct 13, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and discloses real behavior: it is a single-record fetch, an unknown id answers 404, and hidden venues (e.g. NBA arenas) lack a venue-wide match list. It does not cover auth or rate limits, but the error and edge-case disclosure is solid.

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?

One dense paragraph, but it is front-loaded with the core purpose and every clause (return fields, hidden-venue behavior, 404, id provenance) adds distinct information. Slightly heavy but no filler.

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?

There is no output schema, so the description must describe the response — and it does so comprehensively (name, capacity, city, country, coordinates, home teams, match totals, per-sport records). Combined with the error and edge-case coverage, an agent has everything needed to call it 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 schema already documents the single id parameter (baseline 3), but the description adds genuine value by telling the agent where to obtain a valid id from three different sources.

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?

The description states a specific verb+resource ('Returns one venue (stadium or arena)') and enumerates the returned fields, so an agent knows exactly what this fetches. It also implicitly distinguishes itself from venue-events by noting match lists live there, sharpening the boundary with its sibling.

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?

It gives clear provenance for the required id (from search-typed with type venues, from tournament-venues, or from an event's venue) and explains the hidden-venue case routes to per-competition-season data instead. It stops short of an explicit when-not-to-use-this-tool statement.

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

Deploy Server

sofascore_venue

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools