infersports

List Results

list_results

Read-only

Look back at finished-match scores from the 30-day results cache, most-recent-first.

Results-only: each entry is the final score, red cards and finished time (no odds). Unlike the
live tools, these survive a restart — use it for "what was the score of X?" or "yesterday's
results".

Args:
    date: optional UTC kickoff date "YYYY-MM-DD" — the day the match was played.
    team: optional case-insensitive substring matched against either team name.
    league: optional case-insensitive substring matched against the league name.
    limit: max results to return, most-recent-first (1–200, default 50).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`date`	No
`team`	No
`limit`	No
`league`	No

TDQS

A4.8/5.0

Behavior5/5

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

The description elaborates beyond the readOnlyHint annotation by specifying that results include final score, red cards, and finished time (no odds), and that the tool is results-only and persists across restarts. No contradictions with annotations; it adds valuable behavioral context.

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 concise and well-structured: a purpose sentence, a content/behavior sentence, and a bulleted args section. No wasted words; every sentence adds value.

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?

Given the tool's simplicity (no output schema, 4 optional params), the description covers all necessary aspects: data scope (30-day cache), ordering (most-recent-first), content of each entry, and parameter details. It fully equips an agent to use the tool correctly.

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?

Despite 0% schema description coverage, the description provides thorough parameter guidance: date format (YYYY-MM-DD), team as case-insensitive substring, league as case-insensitive substring, and limit with range (1-200) and default (50). This adds essential meaning missing from the schema.

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 states it lists finished-match scores from a 30-day cache, most-recent-first, and distinguishes from live tools by noting it contains no odds and survives restart. The verb 'list' and resource 'results' are explicit, and the usage examples 'what was the score of X?' or 'yesterday's results' further clarify its purpose.

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

Usage Guidelines4/5

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

The description provides clear usage context (checking past scores, yesterday's results) and contrasts with live tools that do not survive restart. However, it does not explicitly name alternative tools like 'get_result' or 'live tools' for when not to use this tool, though the distinction is implied.

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.

TDQS

A4.6/5.0

Disambiguation5/5

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?