Skip to main content
Glama

SportStatsAPI

Get boxing event

get_boxing_event
Read-only

One boxing event with every bout from the main event down: weight class, world titles at stake (WBA, WBC, IBF, WBO, Ring), fighters, result, method (KO, TKO, UD, SD, MD, RTD, DQ, TD, NC, draw), round, time, rounds scheduled.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "event_id": "<event_id>"
    },
    "name": "get_boxing_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_idYesevent code (or number) from get_boxing_events

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / event_id / description
      Previous value: -"event id from get_boxing_events"New value: +"event code (or number) from get_boxing_events"
    • changedInput schema / properties / event_id / type
      Previous value: -"integer"New value: +[
      +  "integer",
      +  "string"
      +]
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and idempotentHint=false, so the safety profile is covered by structured data. The description adds genuinely non-redundant detail by disclosing the returned payload: bout ordering from main event down, titles at stake, and the accepted result methods. It does not describe error behavior for an unknown event id, which is the remaining gap.

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?

A single dense sentence, front-loaded with the core verb and scope, then flowing into the return-field inventory. Nothing is padding, though the compressed abbreviation list (UD, SD, MD, RTD, DQ, TD, NC) is only partially coverage-oriented value and could read as a glossary dump. Overall it is efficient and earns its length.

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?

There is no output schema, so the description must convey what comes back, and it does so thoroughly: bout ordering, weight class, titles, fighters, result, method, round, time, scheduled rounds. That is enough for an agent to decide whether this tool answers a question. The missing pieces are minor: no note on behavior for invalid/unknown ids and no explicit pointer to the listing tool for id discovery.

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 the single event_id parameter is documented in-schema as the code or number from get_boxing_events, so the schema does the heavy lifting. The description body adds nothing about the parameter — no accepted formats beyond what the schema states, no fallback behavior. Baseline 3 is appropriate for a one-parameter tool fully covered by schema documentation.

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?

States a specific resource and scope: 'One boxing event with every bout from the main event down,' which signals single-event, full-card retrieval versus a listing. The field enumeration that follows further pins down what kind of record this is. It stops short of naming the sibling list tool (get_boxing_events) inside the description, leaving that differentiation to the parameter schema.

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

Usage Guidelines3/5

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

Usage is only implied: the description establishes this returns a single event, so an agent can infer it is the follow-up call after a listing search. There is no explicit when-to-use/when-not statement, no prerequisite that the event id must first come from get_boxing_events in the description body, and no mention of related tools like get_boxing_fighter for a different entity.

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