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

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJun 11, 2026

addedInput schema / properties / date_to

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Date To"
+}

AddedJun 9, 2026

TDQS

A5/5.0

Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses timezone handling (day boundaries computed in the given zone, local time added), the truncation/limit behavior, and the inclusive date range with a 31-day cap. This enriches the agent's mental model of side effects and edge cases without contradicting 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 long but every sentence earns its place: purpose, sibling contrast, timezone nuance, truncation, and a clean Args list. The main intent is front-loaded, and the structure guides the reader from general to specific. No 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 tool with 7 parameters, no output schema, and no enums, this description is remarkably complete. It covers all parameter semantics, timezone behavior, range constraints, filtering strategy, and notes the truncation flag. The only minor omission is a full field list of returned fixtures, but the mention of scheduled_at/scheduled_at_local gives sufficient shape for a listing tool.

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 description coverage is 0%, so the description carries the full burden. It explains every parameter with format examples, constraints (e.g., date_to max 31 days, limit 1–200, default 50), and semantic meaning (e.g., timezone for day boundaries, fuzzy league matching). This far exceeds what the bare schema provides.

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 states a specific verb ('List') and resource ('fixtures for a calendar day or range'), and explicitly contrasts with sibling list_today_matches to distinguish scope. It leaves no ambiguity about what the tool does or how it differs from the nearest alternative.

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 provides explicit when-to-use guidance: it names list_today_matches as the alternative for live/today events, explains when to use date_to to cover a tournament window in one call, and advises narrowing with filters rather than paging. This is actionable routing information.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?