Skip to main content
Glama

Search fighters

search_fighters
Read-onlyIdempotent

Use to find a fighter's id by name or nickname (accents optional). Returns weight class, country, pro record, number of fights in the promotion (bouts; ufc_bouts for the UFC only) and last fight date. Costs 1 credit.

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": {
      "query": "<query>"
    },
    "name": "search_fighters"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 20).
queryYesName or nickname, e.g. Topuria or 'El Matador'.
leagueNoLeague. Defaults to mma. One of: mma, pfl, bellator.
weight_classNoe.g. Lightweight, Women's Strawweight.

Output Schema

NameRequiredDescriptionDefault
noteNo
countYes
fightersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / note
      Added value: +{
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent/closed-world, so the description is free to add the things annotations can't: accent-insensitive matching, the credit cost per call, and the distinction between bouts and ufc_bouts in the response. The only missing behavioral note is what happens with an empty result set.

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?

Two compact sentences that front-load purpose and then the return payload plus cost; nothing is padding. The response-field list is slightly dense but earns its place by setting expectations for the caller.

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?

An output schema exists, so enumerating return fields is optional but harmless context. The definition is complete enough to call correctly; the remaining gap is the unstated hand-off to get_fighter once an id is obtained.

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 the parameters are already documented. The description adds only the accent-insensitivity hint for query; it says nothing about league or weight_class scoping that the schema doesn't already carry, 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?

States a specific verb and resource ("find a fighter's id by name or nickname") and even names the field the caller needs back. It implicitly distinguishes itself from get_fighter by being a name-based lookup, but never names that sibling, so an agent must infer that get_fighter is the by-id follow-up.

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?

The phrase "Use to find a fighter's id" implies the search-then-fetch workflow, but the description never states when to prefer this over get_fighter or how to disambiguate multiple matches. No when-not-to-use guidance is given.

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.