Skip to main content
Glama

Paragon Boxing & BJJ Gear Advisor

paragon_glove_size

Read-onlyIdempotent

Return weight-chart matches from Paragon's published Superare S40/S50 sizing dataset. Adult guidance, not competition approval. Optional height flags conflicts; no price, stock or closure claims. Sex selects the source chart and must be provided. Overlapping rows are returned without inventing a single best fit.

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

Input Schema

NameRequiredDescriptionDefault
sexYes
useNo
height_cmNo
weight_kgYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds real behavioral context beyond them: no price/stock/closure claims, height_cm flags conflicts rather than resolving them, and overlapping rows are returned without inventing a single best fit. That is exactly the kind of ambiguity-handling disclosure an agent needs to interpret results.

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?

Five short, front-loaded sentences with no filler; the core lookup is stated first, then scope limits, then parameter behavior. The telegraphic style ('Optional height flags conflicts') is slightly compressed but still parseable.

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

Completeness3/5

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

For a four-parameter lookup with no output schema, the description covers interpretation limits well but leaves two gaps: the effect of the 'use' enum and what a returned row actually contains (size label, weight band, conflicts field). An agent knows how to call it but not fully what it will get back.

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 0%, so the description must carry parameter meaning, and it only partly does: it explains that sex selects the source chart and is required, and that height_cm is optional and flags conflicts. weight_kg is only implied by 'weight-chart', and the 'use' enumeration (bag_or_pads, sparring, competition_training) is never mentioned or explained, leaving a three-value enum with unknown effect.

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: returns weight-chart matches from Paragon's published Superare S40/S50 dataset. Scoping qualifiers ('adult guidance, not competition approval') sharpen what kind of answer it gives. It does not explicitly contrast with siblings like paragon_glove_rules or paragon_gi_size, leaving that separation to inference.

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?

Provides a scope exclusion ('adult guidance, not competition approval') and a hard prerequisite ('sex ... must be provided'), which implies when the tool is appropriate. However, it never names an alternative for rules questions, product comparison, or non-Superare gloves, so routing decisions against the sibling tools are only weakly supported.

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