Skip to main content
Glama

get_dropping_odds

Read-only

Read same-line decimal-price decreases across the latest two retained changes within 24 hours. Requires fresh captures and an upcoming scheduled event. Not a value or arbitrage signal. Stored DraftKings via ESPN only. Keep capture timestamps; offset pages are not a frozen snapshot.

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": "get_dropping_odds"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
sportNo
marketNo
offsetNo
min_drop_pctNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations cover safety (readOnlyHint, non-destructive, closed-world), and the description adds genuinely non-obvious behavior: the comparison is limited to the two most recent retained changes, the window is 24 hours, the data source is DraftKings stored via ESPN only, and offset pages are explicitly not a frozen snapshot. The pagination-instability warning is high-value and would not be derivable from structured fields. It still omits anything about result volume or failure behavior when captures are stale.

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

Conciseness3/5

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

It is compact and front-loads the core operation, with no filler sentences. However, several fragments are cryptic rather than clear — 'Keep capture timestamps' is an opaque directive with no stated consequence, and terms like 'same-line' and 'retained changes' are undefined jargon. Brevity here trades away comprehension.

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

Completeness3/5

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

There is no output schema, five undocumented parameters, and no indication of what a returned drop record looks like, so the description is not complete for the tool's complexity. It does compensate on provenance and data-freshness constraints, which are the hardest things for an agent to guess. What remains missing is parameter meaning and return shape.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across five parameters, so the description carries the full burden and largely fails: limit, sport, market, offset and min_drop_pct are never explained, and the 'latest two retained changes within 24 hours' framing is a fixed rule rather than guidance on how these knobs interact with it. Only the offset remark touches a parameter at all, and it warns about instability rather than defining semantics.

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?

The description gives a specific verb and resource: it reads decimal-price decreases for the same line, measured across the latest two retained price changes within a 24-hour window. That is far more precise than the name alone, and the 'Not a value or arbitrage signal' line rules out a plausible misreading. It does not explicitly contrast itself with siblings like get_odds or get_odds_replay, leaving some differentiation to inference.

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?

It states concrete preconditions ('Requires fresh captures and an upcoming scheduled event') and one negative usage rule ('Not a value or arbitrage signal'), which tells the agent when the tool is applicable and when its output should not be treated as actionable. It stops short of naming an alternative tool for generic or historical odds lookups, so the when-to-use-this-vs-that dimension is incomplete.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.