Skip to main content
Glama

SportStatsAPI

Get MMA event

get_mma_event
Read-only

One MMA card from the main event down (weight class, fighters, winner, method, round, time, judges' scores, fight stats), or with bout_id one fight.

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_mma_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
bout_idNobout code (or number) from a card: that fight with its stats instead
event_idNoevent code (or number) from get_mma_events: the full card

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / bout_id / description
      Previous value: -"bout id from a card: that fight with its stats instead"New value: +"bout code (or number) from a card: that fight with its stats instead"
    • changedInput schema / properties / bout_id / type
      Previous value: -"integer"New value: +[
      +  "integer",
      +  "string"
      +]
    • changedInput schema / properties / event_id / description
      Previous value: -"event id from get_mma_events: the full card"New value: +"event code (or number) from get_mma_events: the full card"
    • changedInput schema / properties / event_id / type
      Previous value: -"integer"New value: +[
      +  "integer",
      +  "string"
      +]
  2. 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 by disclosing the returned payload (weight class, fighters, winner, method, round, time, judges' scores, fight stats), which matters since there is no output schema; it says nothing about auth or rate limits, which is minor for a read tool.

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 front-loaded sentence with the primary mode first and the alternate mode last. The parenthetical field list is long but earns its place given no output schema; 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?

For a two-parameter read tool with full schema coverage and no output schema, the description covers both invocation modes and the shape of the return data. Only the relationship to get_mma_events for discovery is left implicit.

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 coverage is 100%, so both parameters are already documented with their source ('from get_mma_events', 'from a card'). The description restates the same bout_id/event_id mode split without adding format or edge-case detail, so baseline 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 the resource (an MMA card) and enumerates its scope 'from the main event down', plus the alternate single-fight mode. It implicitly separates itself from the list tool get_mma_events, though the sibling name appears only in the schema, not the description.

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?

'or with bout_id one fight' tells the agent how to switch modes, and the schema clarifies event_id comes from get_mma_events. There is no explicit when-not-to-use guidance or statement that get_mma_events should be used for discovery/listing.

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