Skip to main content
Glama

Boxerbook

Search boxers

search_boxers
Read-onlyIdempotent

Find boxers by name (at most 20), best match first: id, slug, name, country, division, record, url. Lists the boxers who share a name or a close spelling. Pass lang matching the user's language (en, es, ru or ja) so the page links match it.

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": {
      "q": "<q>"
    },
    "name": "search_boxers"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesa name or part of it
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

Output Schema

NameRequiredDescriptionDefault
urlNo
citeYesthe markdown link to quote with any fact of this answer: Source: [Boxerbook](<url of the main page>)
as_ofYes
queryNo
partialNotrue when part of the data could not be read this time; retry in a minute for the full answer
resultsYes
attributionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
      +}
  2. Changed3 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"
      +}
    • 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"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "results",
      -  "attribution",
      -  "as_of"
      -]New value: +[
      +  "cite",
      +  "results",
      +  "attribution",
      +  "as_of"
      +]
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the read-only and non-destructive annotations, it discloses the 20-result cap, best-match ordering, fuzzy name matching, and language-dependent page links. These details provide useful expectations for search behavior, though no explicit no-results behavior is given.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loaded with the operation, result limit, and ranking behavior. Each sentence contributes actionable information without unnecessary background or verbosity.

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

Completeness5/5

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

For a simple two-parameter search with full schema coverage, an output schema, and clear safety annotations, this supplies the essential selection and invocation details. Explicit sibling routing would be helpful but is not necessary for correct basic use.

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 already 100%, but the description adds that q can match a close spelling rather than only a name or name fragment. Its lang guidance mostly repeats the schema, so the additional parameter value is useful but limited.

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 clearly states the verb and resource: finding boxers by name, including exact and close-spelling matches. The result cap, ordering, and listed fields further clarify scope, although it does not explicitly distinguish this tool from siblings such as boxer or search.

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?

It gives a clear use case for resolving a shared or approximately spelled boxer name and instructs the agent to match lang to the user's language. It does not explicitly say when to use a sibling instead, such as boxer for a known ID or slug.

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.