Skip to main content
Glama

Paragon Boxing & BJJ Gear Advisor

paragon_compare_products

Read-onlyIdempotent

Compare 2 to 4 known Paragon product handles through the existing read-only Paragon catalog connection. Returns store-provided descriptions, per-variant prices, options and availableForSale with complete bounded pagination. Optional country and language select API context; no physical stock or reservation is implied. Obtain handles from native Shopify catalog tools or product URLs first. Use native Shopify tools for variant selection and commerce.

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": {
      "handles": "<handles>"
    },
    "name": "paragon_compare_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNoKnown destination country. Omission uses the API default context.
handlesYes
languageNoRequested Storefront language code; unsupported context fails explicitly.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / country
      Added value: +{
      +  "description": "Known destination country. Omission uses the API default context.",
      +  "pattern": "^[A-Z]{2}$",
      +  "type": "string"
      +}
    • addedInput schema / properties / language
      Added value: +{
      +  "description": "Requested Storefront language code; unsupported context fails explicitly.",
      +  "pattern": "^[A-Z]{2,3}(?:_[A-Z]{2})?$",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing what comes back (descriptions, per-variant prices, options, availableForSale) and warning that "no physical stock or reservation is implied" — a genuinely useful semantic caveat about availableForSale. It also flags bounded pagination, though "complete bounded pagination" never says what the bound is, and error behavior for bad handles is unstated.

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?

Four dense sentences, front-loaded with the core action and followed by return shape, caveats, and prerequisites in a logical order. Minor redundancy: "read-only" and "no physical stock or reservation" partially restate the readOnlyHint/destructiveHint annotations.

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

Completeness5/5

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

With no output schema, the description carries the return-shape burden and does so explicitly, and it adds the handle-acquisition step an agent otherwise cannot infer. For a read-only comparison tool over 3 parameters, nothing material is missing beyond pagination specifics.

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 67%, and the description fills the main gap by explaining that country and language are optional API context selectors rather than filters on the products. The handle count (2 to 4) is stated in prose, complementing the schema's minItems/maxItems rather than duplicating it.

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 ("Compare 2 to 4 known Paragon product handles") plus the channel ("existing read-only Paragon catalog connection"), so the scope is unambiguous. No sibling does comparison, so an agent can separate this from cart creation, sizing, or purchase-prep tools without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives an explicit prerequisite ("Obtain handles from native Shopify catalog tools or product URLs first") and an explicit exclusion ("Use native Shopify tools for variant selection and commerce"), which tells the agent when not to reach for this tool. The 2-4 handle bound is restated in prose, reinforcing the operating envelope.

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