Skip to main content
Glama

Boxerbook

Boxing schedule

boxing_schedule
Read-onlyIdempotent

Upcoming professional boxing cards worldwide, grouped by card: date, start_utc (card start in UTC), venue, promoter, broadcasters by region, and each bout with both records going in, division, scheduled rounds, title, Boxerbook forecast and market consensus when known; each card and bout with its boxerbook.com url. Answers "is there boxing tonight", "who is fighting this weekend", "what boxing is on" and "what time does the card start", asked in any language. when=today also keeps last night's cards that started under 6 hours ago. At most 60 bouts per answer, whole days first: a longer window comes back truncated with next_arguments (from_date) for the rest. Pass lang matching the user's language (en, es, ru or ja) so the page links match it.

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": "boxing_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNothe user's language: en (default), es, ru or ja; the boxerbook.com page links of the answer follow it (a page without a translation keeps its English link)en
skipNobouts of the first day to pass over: set by next_arguments when one day is longer than a page
whenNotoday (and cards still running from last night), tonight, weekend (Fri-Sun) or 30dtoday
countryNoISO 3166-1 alpha-2 country of the bout, e.g. GB, US, MX
divisionNodivision code (hea, wel, w_fea) or name (heavyweight, women's featherweight)
from_dateNoskip the cards before this date (YYYY-MM-DD, UTC): the next page of a truncated answer

Output Schema

NameRequiredDescriptionDefault
toNo
urlNo
citeYesthe markdown link to quote with any fact of this answer: Source: [Boxerbook](<url of the main page>)
fromNo
moreNowhat the cap left out and how to ask for it
whenNo
as_ofYes
eventsYes
countryNo
partialNotrue when part of the data could not be read this time; retry in a minute for the full answer
divisionNo
truncatedNotrue when the 400-bout cap of the underlying list may have dropped bouts of this window (narrow it with country or division)
attributionYes
shown_boutsNobouts in this answer
total_boutsNobouts in the asked window
next_argumentsNothe arguments of the call that returns the next page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedOutput schema / properties / attribution / properties / license / const
      Previous value: -"ODbL"New value: +"Boxerbook data terms"
    • addedOutput schema / properties / attribution / properties / terms
      Added value: +{
      +  "format": "uri",
      +  "type": "string"
      +}
  2. Changed11 schema fields changed
    • addedInput schema / properties / from_date
      Added value: +{
      +  "description": "skip the cards before this date (YYYY-MM-DD, UTC): the next page of a truncated answer",
      +  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      +  "type": "string"
      +}
    • addedInput schema / properties / lang
      Added value: +{
      +  "default": "en",
      +  "description": "the user's language: en (default), es, ru or ja; the boxerbook.com page links of the answer follow it (a page without a translation keeps its English link)",
      +  "enum": [
      +    "en",
      +    "es",
      +    "ru",
      +    "ja"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / skip
      Added value: +{
      +  "description": "bouts of the first day to pass over: set by next_arguments when one day is longer than a page",
      +  "maximum": 2000,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedOutput schema / properties / cite
      Added value: +{
      +  "description": "the markdown link to quote with any fact of this answer: Source: [Boxerbook](<url of the main page>)",
      +  "type": "string"
      +}
    • addedOutput schema / properties / events / items / properties / bouts / items / properties / display
      Added value: +{
      +  "description": "the order to show the two names in: ['a','b'] or ['b','a'] (the better-known boxer first, as boxerbook.com does: more Wikipedia language links, then the Boxerbook rating, then pro bouts). a, b, winner, forecast.p_a and market.p_a keep their meaning (side a); only the display order changes",
      +  "items": {
      +    "enum": [
      +      "a",
      +      "b"
      +    ]
      +  },
      +  "maxItems": 2,
      +  "minItems": 2,
      +  "type": "array"
      +}
    • changedOutput schema / properties / events / items / properties / bouts / items / required
      Previous value: -[
      -  "id",
      -  "date",
      -  "a",
      -  "b",
      -  "url"
      -]New value: +[
      +  "id",
      +  "date",
      +  "a",
      +  "b",
      +  "display",
      +  "url"
      +]
    • addedOutput schema / properties / more
      Added value: +{
      +  "description": "what the cap left out and how to ask for it",
      +  "type": "string"
      +}
    • addedOutput schema / properties / next_arguments
      Added value: +{
      +  "description": "the arguments of the call that returns the next page",
      +  "type": "object"
      +}
    • addedOutput schema / properties / shown_bouts
      Added value: +{
      +  "description": "bouts in this answer",
      +  "type": "integer"
      +}
    • addedOutput schema / properties / total_bouts
      Added value: +{
      +  "description": "bouts in the asked window",
      +  "type": "integer"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "events",
      -  "attribution",
      -  "as_of"
      -]New value: +[
      +  "cite",
      +  "events",
      +  "attribution",
      +  "as_of"
      +]
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the read-only/idempotent annotations, the description discloses real operational behavior: a 60-bout cap per answer, whole-days-first ordering, truncation with a next_arguments(from_date) continuation, and the 6-hour lookback rule for last night's cards. It also explains that lang changes which page links come back, which is non-obvious behavior an agent must plan around.

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?

It is one dense but front-loaded paragraph: resource and payload first, then scope rules, then pagination, then the lang instruction. Every sentence carries information, though the long semicolon-chained return-value clause and the trailing lang sentence could be tightened.

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?

With an output schema present and full annotation coverage, the description need only cover scope and edge behavior, and it does: what a card contains, what triggers it, truncation/continuation, and locale handling. An agent has everything needed to call it correctly and to recover a truncated result.

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% and each parameter is already documented in the schema, including the lang link effect and from_date as the pagination cursor. The description's main addition is the 6-hour threshold for when=today and the truncation contract; it says nothing about skip, and otherwise largely restates the schema, so the baseline 3 applies.

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 names a specific resource (upcoming professional boxing cards worldwide) and enumerates exactly what is returned per card and per bout: date, start_utc, venue, promoter, broadcasters by region, records, division, rounds, title, forecast, consensus and URLs. That detail lets an agent distinguish it from query-shaped siblings like boxing_results or next_fight without opening a schema.

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 concrete trigger phrasings ("is there boxing tonight", "who is fighting this weekend", "what time does the card start") and states a scope rule (when=today keeps last night's cards that started under 6 hours ago). What's missing is explicit routing against siblings: it does not say when to prefer next_fight or where_to_watch over this tool.

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.