Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sofascore_odds_winning

SofaScore winning odds. Returns SofaScore's winning odds list for a sport: about twenty upcoming events whose favourite SofaScore highlights, each as the usual event summary plus winning_odds (fractional), the expected and actual…

Instructions

SofaScore winning odds. Returns SofaScore's winning odds list for a sport: about twenty upcoming events whose favourite SofaScore highlights, each as the usual event summary plus winning_odds (fractional), the expected and actual percentages SofaScore reports for it (returned as supplied) and the full-time 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 baseball, cricket and 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.5/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 well: it discloses the shape of the return (winning_odds fractional, expected/actual percentages 'returned as supplied', full-time opening/current prices), the meaning of `change` (1 above/-1 below/0 unchanged), and an edge case (404 for sports with no qualifying events). It omits auth/rate-limit context but is otherwise specific.

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 purpose, then escalating detail about the payload and the sport enum. Dense with parentheticals but nearly every clause (change semantics, 404 behavior) carries information; not bloated enough to drop below a 4.

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?

With no output schema, the description must explain returns, and it does: event summary plus the odds fields and market structure are described. Edge-case coverage (404) is a plus. Missing only ancillary operational context for a full 5.

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` param is already documented ('Sport key, or all for every sport. Defaults to all'). The description repeats this verbatim and adds no format or syntax detail beyond it, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Returns SofaScore's winning odds list for a sport') and characterizes the payload (about twenty upcoming events, favourite highlighted). It is clear about what it does, but never names or contrasts with the obvious siblings (sofascore_odds_dropping, sofascore_event_odds), so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit 'use this when' guidance or delineation against alternatives like sofascore_odds_dropping or sofascore_event_odds. The only usage-adjacent content is the sport default and the 404 note, which describe behavior rather than when to pick this tool.

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