Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sofascore_sports

SofaScore supported sports. Lists every sport key the SofaScore endpoints accept (the sport enum of live-events, categories, and scheduled-tournaments), with live and total event counts when available.

Instructions

SofaScore supported sports. Lists every sport key the SofaScore endpoints accept (the sport enum of live-events, categories, and scheduled-tournaments), with live and total event counts when available. The list is fixed and always complete; if the live counts cannot be read, counts_available is false and the per-sport counts are omitted instead of failing the call. Counts are also omitted for a sport the count feed does not cover (for example mma). Accepted sport keys: american-football, aussie-rules, badminton, bandy, baseball, basketball, beach-volley, cricket, darts, esports, floorball, football, futsal, handball, ice-hockey, mma, minifootball, padel, rugby, snooker, table-tennis, tennis, volleyball, waterpolo.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.12

TDQS

A4.1/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 full disclosure and does so well: it states the list is fixed and always complete, explains the `counts_available=false` fallback when live counts can't be read, and notes counts are omitted for sports the feed doesn't cover (e.g. `mma`) instead of failing. This edge-case and failure-mode detail is genuinely beyond structured data, though it does not describe permissions or shape of each entry fully.

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?

Purpose and behavior are front-loaded, and the enumeration of accepted keys, while long, is the payload an agent needs from an enum tool, so it earns its place. Slightly heavy relative to a pure reference endpoint but no wasted sentences.

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

Completeness4/5

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

For a zero-parameter, no-output-schema reference tool the description explains what is returned (sports plus live/total counts and the `counts_available` flag) and covers the main edge cases. It is essentially complete for calling the tool correctly, though it never spells out the intended ordering as a lookup step.

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?

The tool takes zero parameters, so no argument semantics are needed. The description helpfully enumerates the exact accepted sport keys, which compensates for there being no enum in the schema.

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 and resource ('Lists every sport key the SofaScore endpoints accept') and explicitly frames itself as the `sport` enum for live-events, categories, and scheduled-tournaments. An agent can distinguish this reference/lookup tool from sibling data tools 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?

Usage is implied by naming the endpoints that consume the `sport` enum, so an agent can infer this is the place to resolve valid sport keys. However there is no explicit 'use this before calling sofascore_live_events / sofascore_categories' instruction or any exclusion of when not to use it.

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