Skip to main content
Glama

Paragon Boxing & BJJ Gear Advisor

paragon_get_guide_links

Read-onlyIdempotent

Return Paragon's existing sizing, selection or care guide links. Read the linked guide before giving advice. This tool returns references only; it does not infer sizes, retrieve guide contents or determine 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": {
      "topic": "<topic>"
    },
    "name": "paragon_get_guide_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds real value by clarifying the return is references only and that guide contents are not retrieved, but says nothing about output format or behavior when a topic has no guides. With annotations carrying the safety burden, this lands at a solid 3.

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?

Three short sentences with no filler, and the core function is front-loaded before the caveats. Efficient, though the negatives are stacked into one long final sentence.

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?

A single-parameter lookup tool with no output schema; the description covers purpose, a usage instruction, and negative scope well. The main remaining gap is what the returned references look like and whether results can be empty for a topic.

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 0% and there is one enum parameter, so the description must carry meaning. It names three guide categories (sizing, selection, care) that roughly map to the enum values boxing_gloves, bjj_gis, and care, but never states the mapping explicitly or explains which topic yields which guide set.

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 verb and resource ("Return ... guide links") and scopes it to Paragon's existing guides, then explicitly separates itself from inference tools: "does not infer sizes." An agent can distinguish this from sibling sizing tools like paragon_glove_size 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Adds an actionable directive ("Read the linked guide before giving advice") and clear exclusions covering size inference, content retrieval, and competition eligibility. Alternatives are only implied by exclusion rather than named, which keeps it short of a 5.

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