Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sofascore_trending_events

SofaScore trending events. Returns the events trending in one country across every sport (live, recent and upcoming), each as the usual event summary plus its sport key.

Instructions

SofaScore trending events. Returns the events trending in one country across every sport (live, recent and upcoming), each as the usual event summary plus its sport key. country is a two-letter ISO 3166-1 alpha-2 code such as GB or US (any case); SofaScore serves a trending list per country, and a code it does not serve returns 404. The list is about twenty events and changes through the day.

Input Schema

NameRequiredDescriptionDefault
countryYesTwo-letter ISO 3166-1 alpha-2 country code

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.12

TDQS

A4.2/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 behavioral burden and adds useful operational detail: unsupported country codes return 404, the list contains about twenty events, and it changes through the day. It also documents the return shape. It does not mention authentication or rate limits, but for this simple read tool the disclosed behavior is substantive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is four short sentences, front-loaded with the core action and resource. Every sentence adds useful detail: scope, return shape, country-code rules and failure behavior, and list dynamics. There is no filler.

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?

There is no output schema or annotations, so the description must cover enough context for correct invocation. It does well by explaining scope, return shape, parameter format, failure mode, and list size, though the phrase 'usual event summary' assumes known SofaScore event structure rather than fully enumerating return fields.

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 already 100%, so the baseline is 3. The description goes beyond the schema by giving concrete examples (`GB`, `US`), clarifying that case does not matter, and explaining that unsupported country codes return 404, which adds real semantic value for the single parameter.

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 and resource: returns trending events in one country across every sport, covering live, recent, and upcoming items. It also describes the per-event output shape (usual event summary plus a `sport` key), which distinguishes it from sibling tools such as sofascore_trending_players and generic live/scheduled event listings.

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?

It gives clear context that this is a country-specific trending list of about twenty events that changes through the day. However, it does not name alternatives such as sofascore_live_events or sofascore_scheduled_events, nor does it say when not to use this tool. Usage is implied by the word 'trending' rather than explicitly routed.

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