Skip to main content
Glama

SportStatsAPI

Get boxing events

get_boxing_events
Read-only

Boxing events of the last and the current year from Wikipedia: fight cards and world title fights, with date, venue, city, status and the main event's winner (cite the attribution). The current world champions: get_standings with sport boxing.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_boxing_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNocard (a whole card) or title_fight (a world title fight from a champion's record)
limitNomax events (default 20, max 100)
offsetNoskip this many events (paging)
seasonNoyear (default: the last and the current year)
statusNoscheduled, live, finished or no_results
date_toNoYYYY-MM-DD
date_fromNoYYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds value beyond that: the data provenance (Wikipedia), the fields surfaced per event (date, venue, city, status, main-event winner), and an attribution/citation obligation that an agent would otherwise miss. It stops short of explaining pagination behavior or how often the Wikipedia data refreshes.

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?

Two sentences, front-loaded with the resource and scope, then the fallback routing rule. The parenthetical attribution reminder is compact, though its phrasing ('cite the attribution') is slightly oblique and 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?

With no output schema and seven optional parameters, the description does the work of sketching the return shape (fields per event) and the data source. For a read-only listing endpoint that is nearly complete; only paging behavior for the limit/offset pair goes unaddressed.

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?

Schema description coverage is 100%, so every one of the seven parameters is already documented, including kind, season defaults, status values, and the date range. The description adds no syntax, format, or interaction detail beyond what the schema states (its year scope only echoes the schema's season default), so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (boxing events), its scope (last and current year), its source (Wikipedia), and the two record types it returns (fight cards and world title fights). It is clear what the tool does, though it never explicitly contrasts itself with the sibling get_boxing_event (singular), so an agent must infer that this is the list endpoint.

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?

It gives one explicit routing rule: for current world champions, call get_standings with sport boxing. That is genuine when-to-use-this-instead guidance, but it covers only the champion lookup and offers no exclusions or guidance for the closely related get_boxing_event / get_boxing_fighter tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources