Skip to main content
Glama

Paragon Boxing & BJJ Gear Advisor

paragon_gi_size

Read-onlyIdempotent

Return exact height-and-weight matches for A2, A2L and A3 in Paragon's published Ronin guide. Preserve overlaps; do not extrapolate outside the chart, automatically size down, infer stock or certify competition eligibility.

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": {
      "height_cm": "<height_cm>",
      "weight_kg": "<weight_kg>"
    },
    "name": "paragon_gi_size"
  }
}

Input Schema

NameRequiredDescriptionDefault
fitNo
height_cmYes
weight_kgYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the added value here is the explicit list of things the tool refuses to do: extrapolate beyond the chart, auto-size down, infer stock, or certify competition eligibility. Those are genuine behavioral disclosures an agent would otherwise have to discover by trial, though the description stops short of saying what a no-match result looks like.

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 sentences: purpose first, guardrails second, with no filler. The do-not list is slightly ambiguous in construction, since 'automatically size down' sits inside a comma series following 'do not extrapolate', which momentarily reads as an affirmative action rather than a prohibition.

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 read-only lookup with no output schema, the definition covers what is returned conceptually (exact matches, overlaps preserved) and where the data comes from. Remaining gaps are the unexplained 'fit' parameter and the absence of any statement about units or empty-result behavior, neither of which is fatal given the constrained, closed-world schema.

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 carries the full burden. It adds meaningful matching semantics for height_cm and weight_kg (exact matches only, overlaps preserved, no extrapolation), but the third parameter, the 'fit' enum (competition/training), is never mentioned and its effect is left completely unexplained.

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?

The description names a specific verb ('Return'), resource ('exact height-and-weight matches'), scope ('A2, A2L and A3 in Paragon's published Ronin guide'), and the guide it draws from. That is enough for an agent to tell this apart from paragon_glove_size or the guide-link tools without opening any schema.

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 description gives hard boundaries for use ('do not extrapolate outside the chart', 'do not automatically size down'), which implicitly tells the agent when the tool is inappropriate. However, it never names an alternative tool or says 'use this when you want X versus Y', so routing guidance is only implied.

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