infersports

List Events (day or date range)

list_events

Read-only

List the fixtures for a calendar day — or a bounded [date, date_to] range.

Unlike list_today_matches (today + anything still live), this is a strict window for whatever
``date`` you ask for. Pass ``date_to`` (inclusive, max 31 days after ``date``) to cover a whole
tournament window in ONE call — "all group-stage matches June 11–28" needs no per-day loop. UTC
is canonical: pass an IANA ``timezone`` and the day boundaries are computed in that zone (so
"June 12 in Shanghai" excludes a match that is still June 11 / already June 13 locally); each
fixture keeps its UTC ``scheduled_at`` and adds ``scheduled_at_local``. Capped to ``limit``
(``truncated`` flags overflow) — narrow with sport/status/league rather than paging.

Args:
    date: REQUIRED calendar day "YYYY-MM-DD" (e.g. "2026-06-12") — the window start.
    date_to: optional inclusive end day "YYYY-MM-DD" (max 31 days after ``date``); omit for a
        single day.
    timezone: optional IANA timezone (e.g. "Asia/Shanghai", "America/New_York") for the day
        boundary; default is the UTC day.
    sport: optional filter — "football" or "basketball".
    status: optional filter — "scheduled", "live" or "finished".
    league: optional league filter — a name (fuzzy-matched, e.g. "World Cup") or an external id ("lg_…").
    limit: max fixtures to return (1–200, default 50).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`date`	Yes
`limit`	No
`sport`	No
`league`	No
`status`	No
`date_to`	No
`timezone`	No

TDQS

A4.8/5.0

Behavior5/5

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

Annotations declare readOnlyHint=true, and description adds context on timezone handling, truncation, and return fields (scheduled_at, scheduled_at_local). No contradiction.

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

Conciseness4/5

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

Well-structured with purpose first, then parameter breakdown. Slightly verbose but each sentence adds value. Could be tighter.

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?

Comprehensive for a 7-parameter tool with no output schema. Explains return fields and filtering strategies, though output structure is not fully specified.

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

Parameters5/5

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

Schema provides 0% description coverage. Description explains all 7 parameters in detail with examples, defaults, and constraints (e.g., max 31 days for date_to, limit 1-200).

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?

Clearly states it lists fixtures for a calendar day or date range. Distinguishes from sibling tool list_today_matches by explaining the difference in window behavior.

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 contrasts with list_today_matches, explains when to use date_to for tournament windows, and advises on filtering rather than paging.

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

All infersports 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.

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.

Naming Consistency5/5

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.

Tool Count5/5

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.

Completeness5/5

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.

Resources

Need Help?