Skip to main content
Glama

Paragon Boxing & BJJ Gear Advisor

paragon_glove_rules

Read-onlyIdempotent

Source-linked competition glove rules for World Boxing, IBA, England Boxing, Boxing Canada, ABC professional guidance and BBBofC. Explicit sex and age group required. Returns no definitive weight where an event exception, unsupported category or unverified current source prevents it. Body weight alone does not establish the entered division. Never use this as proof a glove brand or model is approved.

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": {
      "federation": "<federation>",
      "weight_kg": "<weight_kg>",
      "sex": "<sex>",
      "age_group": "<age_group>"
    },
    "name": "paragon_glove_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
sexYes
age_groupYes
weight_kgYes
federationYes
opponent_weight_kgNo
event_rules_confirmedNoFor IBA elite men: whether the organiser confirmed the general 10/12 oz table applies rather than IBA-owned event exceptions.
competition_category_kgNoEntered division's upper weight limit, if known. Required for a definite weight-based amateur category lookup. Not a boxer's current body weight.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish this as a safe, read-only, idempotent, closed-world lookup, so the safety profile is covered. The description adds meaningful behavioral context the annotations cannot: results are source-linked, no definitive weight is returned where an event exception or unsupported category applies, and the output is not evidence of equipment approval. It does not describe output shape, but no output schema exists and the failure-mode behavior is disclosed, which is the higher-value disclosure here.

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?

Four tight sentences, front-loaded with the resource and coverage, then requirements, then failure modes, then the misuse warning. No sentence repeats the schema or wastes words.

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 seven-parameter lookup with no output schema, the description covers purpose, required inputs, the key parameter distinction, and degraded-result conditions. The remaining gap is unelaborated optional parameters and the absence of any statement about the structure of returned rules, which keeps it short of full completeness.

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 low at 29%, and the description compensates for the most consequential ambiguity: 'Body weight alone does not establish the entered division' explains the relationship between weight_kg and competition_category_kg. It also reinforces that sex and age_group are mandatory. However, it adds nothing about opponent_weight_kg, event_rules_confirmed, or the federation enum beyond what the schema names, leaving real gaps at this coverage level.

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?

States a specific resource — source-linked competition glove rules — and enumerates the governed federations (World Boxing, IBA, England Boxing, Boxing Canada, ABC, BBBofC), so the agent knows this is a rules-lookup tool, not a sizing or product tool. The closing line ('Never use this as proof a glove brand or model is approved') distinguishes it from product-approval siblings without needing their names.

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 concrete preconditions ('Explicit sex and age group required') and a hard exclusion ('Never use this as proof a glove brand or model is approved'), plus an implicit instruction that body weight alone is insufficient for division lookup. It never names paragon_glove_size or paragon_compare_products as alternatives, so rival selection is left to inference.

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