Skip to main content
Glama

Boxerbook

Division rankings

rankings
Read-onlyIdempotent

The top 15 of a division: the Boxerbook rating (default) or the latest list of a publisher (WBC, WBA, IBF, WBO, The Ring, TBRB), with records. Division by code (hea, wel, w_fea) or name (heavyweight, women's flyweight). Pound for pound: division p4p (or "pound for pound", pfp) gives the Boxerbook P4P top 25 of men, w_p4p (or "women's p4p") the top 15 of women, ranked by the Boxerbook rating (mu − 2·rd measured against the elite of the boxer's division; active within 18 months, 10+ bouts, 2+ quality wins in 36 months); only Boxerbook has a P4P list, no publisher's is stored. 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": {
      "division": "<division>"
    },
    "name": "rankings"
  }
}

Input Schema

NameRequiredDescriptionDefault
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
divisionYesdivision code (hea, wel, w_fea) or name (heavyweight, women's featherweight)
publisherNoboxerbook (the Boxerbook rating), wbc, wba, ibf, wbo, ring, tbrb or wban (WBAN World Ratings, women only)boxerbook

Output Schema

NameRequiredDescriptionDefault
urlNo
citeYesthe markdown link to quote with any fact of this answer: Source: [Boxerbook](<url of the main page>)
as_ofYes
itemsYes
partialNotrue when part of the data could not be read this time; retry in a minute for the full answer
divisionYes
list_dateNo
publisherYes
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
    • changedInput schema / properties / publisher / description
      Previous value: -"boxerbook (the Boxerbook rating), wbc, wba, ibf, wbo, ring or tbrb"New value: +"boxerbook (the Boxerbook rating), wbc, wba, ibf, wbo, ring, tbrb or wban (WBAN World Ratings, women only)"
    • changedInput schema / properties / publisher / enum
      Previous value: -[
      -  "boxerbook",
      -  "wbc",
      -  "wba",
      -  "ibf",
      -  "wbo",
      -  "ring",
      -  "tbrb"
      -]New value: +[
      +  "boxerbook",
      +  "wbc",
      +  "wba",
      +  "ibf",
      +  "wbo",
      +  "ring",
      +  "tbrb",
      +  "wban"
      +]
    • changedOutput schema / properties / publisher / enum
      Previous value: -[
      -  "boxerbook",
      -  "wbc",
      -  "wba",
      -  "ibf",
      -  "wbo",
      -  "ring",
      -  "tbrb"
      -]New value: +[
      +  "boxerbook",
      +  "wbc",
      +  "wba",
      +  "ibf",
      +  "wbo",
      +  "ring",
      +  "tbrb",
      +  "wban"
      +]
  3. Changed4 schema fields changed
    • addedOutput schema / properties / items / items / properties / division
      Added value: +{
      +  "description": "pound for pound only: the boxer's Boxerbook rating division code",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / items / items / properties / last_bout_date
      Added value: +{
      +  "description": "pound for pound only",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / items / items / properties / quality_wins
      Added value: +{
      +  "description": "pound for pound only: wins in the last 36 months over opponents rated like a division top-15 boxer at the time",
      +  "type": "integer"
      +}
    • addedOutput schema / properties / items / items / properties / score
      Added value: +{
      +  "description": "pound for pound only: the P4P score, the order of the list: mu − 2·rd measured against the elite of the boxer's division (method at /rankings/p4p#how)",
      +  "type": "number"
      +}
  4. Changed4 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"
      +}
    • addedOutput schema / properties / items / items / properties / url
      Added value: +{
      +  "description": "the boxer's boxerbook.com page",
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "division",
      -  "publisher",
      -  "items",
      -  "attribution",
      -  "as_of"
      -]New value: +[
      +  "cite",
      +  "division",
      +  "publisher",
      +  "items",
      +  "attribution",
      +  "as_of"
      +]
  5. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world, and the description still adds substantive behavior: list sizes (15 vs 25), the eligibility rules behind the Boxerbook rating (active within 18 months, 10+ bouts, 2+ quality wins in 36 months), and the hard constraint that no publisher P4P list exists. That last point prevents a whole class of failing calls.

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?

Purpose is front-loaded and every clause carries information — codes, aliases, list sizes, eligibility rules, language linking. It is dense and slightly overstuffed in the parenthetical rating formula, but nothing is redundant filler.

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 return values need not be explained, and the description covers all three parameters plus the special P4P cases. The only real gap is the missing wban publisher mention, which leaves a small mismatch with the enum an agent will see.

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 100%, so 3 is the baseline, but the description goes further by supplying alias values for division (p4p, 'pound for pound', pfp, w_p4p) that the schema's plain string field cannot express, and by constraining publisher to Boxerbook when a P4P division is used. Minor deduction: the publisher list in the prose omits wban, which the schema enum includes.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb-and-resource statement — 'The top 15 of a division' — then names the two modes (Boxerbook rating vs. a named publisher list) and the P4P variants. An agent can tell exactly what comes back and how it differs from siblings like boxer or search_boxers, which return entities rather than ranked lists.

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?

Gives clear selection guidance inside the tool: division by code or name, publisher choice, and the special p4p/w_p4p division values, plus a directive to pass lang matching the user's language. It does not address when to prefer this over a sibling tool, but the sibling set covers different resources so the risk of misrouting is low.

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.