list_bookmakersList the bookmakers available on your tier.
Returns the curated catalogue (each with ``key``, ``name`` and ``class`` = "sharp" | "asian")
plus a ``note`` on tier coverage. Free tier excludes the sharp book (Pinnacle). Use the returned
``key`` values in the ``bookmakers`` filter of get_match_odds / compare_lines.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations provide readOnlyHint=true, which the description aligns with ('List'). The description adds behavioral details: returns curated catalogue with key, name, class, and a note on tier coverage. This goes beyond the annotation's simple safety hint.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is three concise sentences, front-loaded with purpose and output details. No wasted words; every sentence provides useful information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema, the description fully explains the return structure and usage context. It addresses tier variability (free tier exclusion) and downstream tool integration, making it complete for a simple list tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are no parameters, and the schema is fully covered (100%). The description adds value by describing the output structure (key, name, class, note) and how to use it, which the empty schema does not convey.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool lists bookmakers available on the user's tier, specifying the verb 'list' and resource 'bookmakers'. It distinguishes from sibling tools by focusing on bookmaker listing, which is unique among siblings like get_match_odds or compare_lines.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly tells when to use the tool: to obtain bookmaker keys for use in get_match_odds or compare_lines. It also provides a note about free tier exclusion of Pinnacle, guiding appropriate usage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: compare_lines contrasts bookmakers, compare_prob evaluates external probabilities, find_arbitrage detects arbitrage opportunities, find_match resolves fixtures, etc. Even related tools like get_sharp_line (one-call line) and compare_lines (event_id-based comparison) are complementary rather than overlapping. No ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., compare_lines, find_match, list_bookmakers). Verbs like compare, find, get, list, scan, score are uniform. No mixing of conventions or vague names.
With 17 tools covering fixture discovery, odds retrieval, comparisons, value/arb detection, line movement, results, and slate scanning, the count is well-scoped for a sports betting odds API. No unnecessary tools, and the set feels complete without being bloated.
The tool surface covers the full lifecycle: find matches (find_match, list_events, list_today_matches), get odds (get_match_odds, get_sharp_line, compare_lines), detect value/arb (find_value, find_arbitrage, scan_slate), analyze lines (get_opening_line, explain_handicap, score_prob), and retrieve results (get_result, list_results). No obvious gaps for the stated read-only odds analysis domain.