Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

sofascore_odds_dropping

Read-only

Returns SofaScore's dropping odds list: about twenty upcoming events whose odds moved most, with the choice and percentage SofaScore reports and the market with opening and current prices. Optional sport (all by default, or a sport key from sofascore_sports); a sport with no qualifying events returns not found.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sofascore_odds_dropping"
  }
}

Input Schema

NameRequiredDescriptionDefault
sportNoOptional. One of all, 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. Defaults to all. A sport with no qualifying events at the moment returns not found.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds useful behavior beyond that: the list size (~twenty events), the fields returned (choice, percentage, market with opening/current prices), and the not-found outcome when a sport has no qualifying events.

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?

Two tight sentences with the core purpose and return contents front-loaded, followed by the only parameter's semantics. No filler and nothing repeated unnecessarily.

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 annotations covering the safety profile and an output schema handling return structure, the description is nearly complete for a single-optional-param tool. The only minor gap is not routing the agent away from the closely related sofascore_odds_winning sibling.

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 schema already documents the enum values, default of 'all', and the not-found behavior. The description restates the same semantics (optional, default all, sport key from sofascore_sports) without adding new syntax or constraints, so the baseline 3 applies.

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') and immediately defines contents: ~twenty upcoming events whose odds moved most, with choice, percentage, and market prices. An agent can distinguish this from siblings like sofascore_odds_winning 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 Guidelines4/5

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

Explains the optional sport parameter's default ('all by default', or a key from sofascore_sports), giving clear context for when to pass it. It does not, however, contrast this tool with sibling odds tools (e.g., sofascore_odds_winning) or state 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.

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources