Skip to main content
Glama

skipodds

by com.skipodds

List fixtures

list_fixtures
Read-only

Upcoming and recent fixtures with fair win probabilities: every surveyed bookmaker price averaged and stripped of its margin (de-vigged), so probabilities sum to exactly 100%. 13 sports, 69+ bookmakers. START HERE — the fixture ids returned are what get_fixture and get_fixture_movement require. Use get_fixture instead when you already hold an id, and list_tournament_outrights for who-wins-the-competition rather than individual matches. "recent" means a kickoff within the last 6 hours for soccer and tennis, 8 hours for basketball, baseball, hockey, American football, MMA and boxing, and 12 hours for cricket and rugby; anything older has rolled off the board. Outright/tournament-winner markets exist for soccer and golf only — every other sport is fixture-level. Read-only. Returns an empty list, not an error, when nothing is scheduled in range.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum fixtures to return. Defaults to 10; raise it to widen the window rather than calling repeatedly.
sportNoWhich 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.
competitionNoRestrict to one soccer competition by slug, e.g. "premier-league-2026". Soccer only — ignored for other sports. Slugs appear on the fixtures this tool returns, so call once without it to discover them.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceNo
fixturesYesOne entry per fixture. Empty when nothing is scheduled in range — not an error.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "fixtures": {
+      "description": "One entry per fixture. Empty when nothing is scheduled in range — not an error.",
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "id": {
+            "description": "Pass to get_fixture or get_fixture_movement.",
+            "type": "string"
+          },
+          "skipodds": {
+            "additionalProperties": true,
+            "description": "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.",
+            "properties": {
+              "books_surveyed": {
+                "description": "Distinct bookmaker brands averaged.",
+                "type": "integer"
+              },
+              "fair_odds": {
+                "description": "Decimal odds equivalent of each probability.",
+                "type": "object"
+              },
+              "margin_removed": {
+                "description": "Bookmaker margin stripped, as a decimal (0.052 = 5.2%).",
+                "type": "number"
+              }
+            },
+            "type": "object"
+          },
+          "status": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "source": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "fixtures"
+  ],
+  "type": "object"
+}
  2. Changed5 schema fields changed
    • changedInput schema / properties / competition / description
      Previous value: -"Soccer competition slug, e.g. premier-league-2026 (soccer only)."New value: +"Restrict to one soccer competition by slug, e.g. \"premier-league-2026\". Soccer only — ignored for other sports. Slugs appear on the fixtures this tool returns, so call once without it to discover them."
    • addedInput schema / properties / limit / default
      Added value: +10
    • changedInput schema / properties / limit / description
      Previous value: -"Max fixtures to return (default 10)."New value: +"Maximum fixtures to return. Defaults to 10; raise it to widen the window rather than calling repeatedly."
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / sport / description
      Previous value: -"Omit for soccer. Any other sport must be named explicitly."New value: +"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."
  3. Changed1 schema field changed
    • changedInput schema / properties / competition / description
      Previous value: -"Soccer competition slug, e.g. fifa-world-cup-2026 (soccer only)."New value: +"Soccer competition slug, e.g. premier-league-2026 (soccer only)."
  4. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnlyHint=true annotation, the description adds rich behavioral context: probabilities are de-vigged to sum to 100%, "recent" has specific kickoff windows per sport, outright markets are limited to soccer and golf, and the tool returns an empty list rather than an error when nothing is scheduled. No contradiction with annotations.

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?

The description is dense but every sentence serves a purpose: core function, coverage scope, usage priority, sibling guidance, time windows, market exceptions, and empty-list behavior. It is front-loaded with the most important information and avoids fluff.

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?

The description covers all key aspects: what the tool returns (fixtures with probabilities), how to use the returned IDs, when to use alternatives, what "recent" means, sport coverage, outright-market limitations, and empty-list behavior. This is complete for the tool's complexity even with an output schema present.

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 thorough descriptions for all three parameters (limit, sport, competition), achieving 100% coverage. The description does not add significant parameter-specific meaning beyond what the schema already states, so the baseline score of 3 is appropriate.

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 opens with a specific verb+resource: "Upcoming and recent fixtures with fair win probabilities" and explains the de-vigging process. It clearly distinguishes itself from siblings by stating "START HERE" and explicitly naming get_fixture and list_tournament_outrights as alternatives for different use cases.

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?

The description explicitly states when to use this tool vs alternatives: "Use get_fixture instead when you already hold an id, and list_tournament_outrights for who-wins-the-competition rather than individual matches." It also clarifies the "recent" window per sport, giving concrete context for when data is available.

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

All skipodds toolsInspect
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