skipodds

Get one fixture

get_fixture

Read-only

One fixture in full: fair probability and fair odds for every outcome, how many bookmakers were surveyed, and when the consensus last updated. Use when you already have a fixture id; call list_fixtures first if you do not. Use get_fixture_movement instead when you need how the price CHANGED rather than where it stands now. Read-only. An id that is unknown or has rolled off the board returns a fixture_not_found error rather than an empty fixture, and a low bookmaker count means a thin market rather than a failure.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Fixture id, exactly as returned by list_fixtures. An opaque string — never construct, guess, or derive one from team names or dates; ids are not stable across sports namespaces.
`sport`	No	Which sport to query. Omit entirely for soccer, which is the default; every other sport must be named explicitly. Note "football" means American football and "rugby" covers union.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	No
`status`	No
`skipodds`	No	De-vigged probabilities for this market. Keys vary by sport: home/draw/away for team sports, p1/p2 for tennis and fights, players[] for golf.

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description adds concrete behavioral expectations: unknown or rolled-off ids produce a fixture_not_found error rather than an empty fixture, and a low bookmaker count means a thin market rather than failure. This equips the agent with edge-case handling.

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?

Three sentences, each with a distinct role: what the tool returns, when to use it (and when not), and edge-case behavior. Every sentence earns its place with no redundancy or filler.

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

Completeness5/5

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

For a single-fixture retrieval with a rich output schema, the description covers purpose, usage preconditions, alternatives, and error semantics. It is complete enough for an agent to select and invoke the tool correctly without additional context.

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?

The input schema already provides 100% parameter coverage, including id provenance and sport enum semantics, so the description correctly doesn't repeat those details. The description does not add further param-specific meaning, which is acceptable given the schema's completeness.

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?

The description clearly identifies the tool's function: retrieving a single fixture in full with fair probability, fair odds, bookmaker count, and consensus update time. It distinguishes itself from siblings by naming get_fixture_movement for price changes and list_fixtures for obtaining ids.

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

Usage Guidelines5/5

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

Explicitly states when to use: when you already have a fixture id, and directs those without one to call list_fixtures first. It also names the alternative tool for price changes (get_fixture_movement), providing a clear when-not-to-use rule.

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

All skipodds tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.8/5.0

Disambiguation5/5

Each tool targets a distinct resource and action: fixture current state vs. movement, fixture listing vs. tournament/outright listings, and golf tournaments vs. soccer tournaments are explicitly separated. The descriptions cross-reference each other to prevent confusion.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern: get_fixture, get_fixture_movement, list_fixtures, list_golf_tournaments, list_tournament_outrights. The naming is predictable and clearly hierarchical.

Tool Count5/5

Five tools cover the server's purpose without bloat. The scope is focused on reading odds data, and each tool earns its place: current fixture, fixture movement, fixture list, and the two outright market lists.

Completeness5/5

The surface covers the full read-only workflow: discover fixtures, inspect current odds, examine movement, and access tournament outrights for the sports that have them. No major gaps are apparent, and the descriptions explicitly note unsupported sports to avoid dead ends.

Resources

Need Help?