Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sofascore_odds_dropping

SofaScore dropping odds. Returns SofaScore's dropping odds list for a sport: about twenty upcoming events whose odds moved most, each as the usual event summary plus the choice_name and percentage SofaScore reports for the move…

Instructions

SofaScore dropping odds. Returns SofaScore's dropping odds list for a sport: about twenty upcoming events whose odds moved most, each as the usual event summary plus the choice_name and percentage SofaScore reports for the move (returned as supplied) and the market with opening and current prices (change is 1 above the opening price, -1 below it, 0 unchanged). The sport enum accepts all and the SofaScore sport keys; it defaults to all. A sport with no qualifying events at the moment (for example esports when probed) returns 404.

Input Schema

NameRequiredDescriptionDefault
sportNoSport key, or all for every sport. Defaults to all

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.12

TDQS

A3.9/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 does so well: it discloses return structure (event summary plus choice_name/percentage plus market with opening/current prices), the `change` flag semantics (1/-1/0), and the 404 behavior for sports with no qualifying events. It omits auth/rate-limit context, keeping it short of a 5.

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, then details in a logical order (payload, change semantics, param default, 404). Dense but each clause carries information; the parentheticals are slightly heavy but not wasteful.

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?

No output schema or annotations exist, yet the description explains the return shape and the 404 edge case that an agent would otherwise hit blind. The only gap is the lack of guidance on choosing this over sibling odds endpoints.

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 `sport` enum is fully documented in the schema, so the baseline is 3. The description restates the enum accepts `all` and SofaScore sport keys and defaults to `all`, adding no syntax or meaning beyond 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 ('Returns SofaScore's dropping odds list for a sport') and adds scope ('about twenty upcoming events whose odds moved most'). This distinguishes it from the sibling sofascore_odds_winning without needing 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 clearly (fetch the dropping-odds list per sport) and the 404-for-no-events case is flagged, but no explicit when-to-use vs the winning-odds sibling or other odds tools is given. No exclusions or alternatives named, so this is adequate but leaves routing to inference.

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