Skip to main content
Glama

Boxerbook

Where to watch

where_to_watch
Read-onlyIdempotent

Where to watch a fight and when it starts: the broadcasters (platform, region, link) of a bout or of a whole card, with the card start time in UTC and the boxerbook.com url of the bout or card; or, with platform (e.g. "DAZN", "ProBox TV"), what is on that platform: its upcoming cards and those of the last 12 months. Answers "where can I watch A vs B", "what channel is the fight on" and "what time does it start", asked in any language. Give bout_id, event_id, query (two boxers "A vs B", or one boxer for the next bout) or platform. An empty list means none is on record yet. hub_url is the site's «Where to watch boxing this week» page. 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": "where_to_watch"
  }
}

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
queryNoinstead of an id: two boxers as "A vs B" (their scheduled bout, else their latest), or one boxer by name (the next bout on record)
bout_idNoBoxerbook bout id
event_idNoBoxerbook event (card) id
platformNoinstead of an id: a broadcast or streaming platform by name, e.g. DAZN, ESPN+, ProBox TV, BXNG TV

Output Schema

NameRequiredDescriptionDefault
idNo
urlYes
citeYesthe markdown link to quote with any fact of this answer: Source: [Boxerbook](<url of the main page>)
cityNo
dateNo
kindYes
noteNo
as_ofYesISO UTC time of this answer
boutsNo
titleYes
venueNo
recentNokind platform: its cards of the last 12 months, newest first (at most 10)
statusNo
countryNo
hub_urlNothe «Where to watch boxing this week» page
partialNotrue when part of the data could not be read this time; retry in a minute for the full answer
event_idNo
platformNokind platform: the platform (kind: subscription, free, ppv or promoter; small: a small or mid-size platform; home: its website)
upcomingNokind platform: its cards to come, nearest first
start_utcNoISO UTC start of the card, when known
broadcastsYes
attributionYes
platform_pagesNothe boxerbook.com page of each listed platform

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / query
      Added value: +{
      +  "description": "instead of an id: two boxers as \"A vs B\" (their scheduled bout, else their latest), or one boxer by name (the next bout on record)",
      +  "maxLength": 120,
      +  "minLength": 2,
      +  "type": "string"
      +}
  2. 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"
      +}
  3. Changed10 schema fields changed
    • 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 / platform
      Added value: +{
      +  "description": "instead of an id: a broadcast or streaming platform by name, e.g. DAZN, ESPN+, ProBox TV, BXNG TV",
      +  "maxLength": 60,
      +  "minLength": 2,
      +  "type": "string"
      +}
    • 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 / hub_url
      Added value: +{
      +  "description": "the «Where to watch boxing this week» page",
      +  "type": "string"
      +}
    • changedOutput schema / properties / kind / enum
      Previous value: -[
      -  "bout",
      -  "event"
      -]New value: +[
      +  "bout",
      +  "event",
      +  "platform"
      +]
    • addedOutput schema / properties / platform
      Added value: +{
      +  "description": "kind platform: the platform (kind: subscription, free, ppv or promoter; small: a small or mid-size platform; home: its website)",
      +  "properties": {
      +    "home": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "kind": {
      +      "type": "string"
      +    },
      +    "name": {
      +      "type": "string"
      +    },
      +    "small": {
      +      "type": "boolean"
      +    }
      +  },
      +  "required": [
      +    "name",
      +    "kind"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / platform_pages
      Added value: +{
      +  "description": "the boxerbook.com page of each listed platform",
      +  "items": {
      +    "properties": {
      +      "platform": {
      +        "type": "string"
      +      },
      +      "url": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "platform",
      +      "url"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / recent
      Added value: +{
      +  "description": "kind platform: its cards of the last 12 months, newest first (at most 10)",
      +  "items": {
      +    "properties": {
      +      "city": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "country": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "date": {
      +        "type": "string"
      +      },
      +      "event_id": {
      +        "type": "integer"
      +      },
      +      "regions": {
      +        "items": {
      +          "type": "string"
      +        },
      +        "type": "array"
      +      },
      +      "start_utc": {
      +        "description": "ISO UTC start of the card, when known",
      +        "type": "string"
      +      },
      +      "title": {
      +        "description": "the main bout, else the venue",
      +        "type": "string"
      +      },
      +      "url": {
      +        "type": "string"
      +      },
      +      "venue": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      }
      +    },
      +    "required": [
      +      "event_id",
      +      "date",
      +      "title",
      +      "url"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / upcoming
      Added value: +{
      +  "description": "kind platform: its cards to come, nearest first",
      +  "items": {
      +    "properties": {
      +      "city": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "country": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "date": {
      +        "type": "string"
      +      },
      +      "event_id": {
      +        "type": "integer"
      +      },
      +      "regions": {
      +        "items": {
      +          "type": "string"
      +        },
      +        "type": "array"
      +      },
      +      "start_utc": {
      +        "description": "ISO UTC start of the card, when known",
      +        "type": "string"
      +      },
      +      "title": {
      +        "description": "the main bout, else the venue",
      +        "type": "string"
      +      },
      +      "url": {
      +        "type": "string"
      +      },
      +      "venue": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      }
      +    },
      +    "required": [
      +      "event_id",
      +      "date",
      +      "title",
      +      "url"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "kind",
      -  "id",
      -  "title",
      -  "broadcasts",
      -  "url",
      -  "attribution",
      -  "as_of"
      -]New value: +[
      +  "cite",
      +  "kind",
      +  "title",
      +  "broadcasts",
      +  "url",
      +  "attribution",
      +  "as_of"
      +]
  4. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful behavior: an empty list means nothing is on record, hub_url is the weekly page, and lang changes the returned page links. It does not discuss rate limits or result ordering, keeping it at 4.

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?

Front-loaded with the core purpose and the two modes, and every clause carries information. The sentences are long and dense with parentheticals, which slightly hurts scannability, but nothing is redundant.

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 an output schema present, return values needn't be spelled out, and the description still covers the empty-result case and the hub_url field. For a 5-parameter, multi-mode tool it is nearly complete; only the precedence between id and query inputs is left implicit.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: query accepts 'A vs B' (scheduled bout, else latest) or a single boxer (next bout), platform returns upcoming cards plus the last 12 months, and lang controls link localization. That is value beyond the schema's own text.

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?

States a specific verb+resource ('where to watch a fight and when it starts') and enumerates the two operating modes: broadcaster lookup by bout/card, and platform listing. An agent can distinguish this from siblings like boxing_schedule or next_fight without opening the 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?

Gives concrete trigger questions ('where can I watch A vs B', 'what channel is the fight on', 'what time does it start') and explains the input alternatives (bout_id, event_id, query, platform). It does not explicitly name a sibling tool to use instead, so it stops short of a 5.

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.