Skip to main content
Glama

SportStatsAPI

Get MMA events

get_mma_events
Read-only

MMA (UFC) fight cards by date: name, date, status and the main event with its result once known.

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

Input Schema

NameRequiredDescriptionDefault
limitNomax events (default 20, max 100)
offsetNoskip this many events (paging)
statusNoscheduled, live, finished or cancelled
date_toNoevents on or before YYYY-MM-DD
date_fromNoevents on or after YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, so safety is covered. The description does add real behavior beyond that: it enumerates the returned fields and notes the main-event result appears 'once known', disclosing that records can be incomplete. It says nothing about ordering, default page size, or what an empty result means.

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 a colon list of returned fields — no filler. The phrasing 'by date: name, date, status' is slightly compressed and reads ambiguously on first pass, which keeps it from a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter listing tool with no output schema finished beyond a one-line field list and no annotation coverage of pagination, the description should explain paging behavior and how it relates to get_mma_event. The lack of any sibling differentiation leaves a real routing gap for an agent choosing among ~30 sports tools.

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 all five parameters (limit, offset, status, date_from, date_to) are already documented in the schema. The description echoes date and status filtering but adds no syntax, format, or interaction detail beyond that, so the 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?

States a specific resource (MMA/UFC fight cards) and scope (listed by date), plus the fields returned. It is clear what the tool does, but it never distinguishes itself from the sibling get_mma_event (singular), so an agent must guess which one returns a single card.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no pointer to the singular get_mma_event or get_mma_fighter siblings. 'By date' faintly implies browsing a schedule, but nothing tells the agent when this listing tool is preferable to the detail 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.

Resources