Skip to main content
Glama

Get RoutersUA product details

routersua_get_product
Read-onlyIdempotent

Return the full details of one RoutersUA product (description, specifications, photos, price in UAH, availability, backorder ship date when on backorder) with a photo attached as an image and a cart_url that opens the store checkout with one piece of it in the cart; price and availability are read live. Use it when the user names one product or after routersua_search_products; for two or more products side by side use routersua_compare_products, and for several products or quantities in one cart routersua_create_cart_link. Pass product as the slug from search results, the model code (GL-MT6000), the store code (RUA-GL-MT6000) or the GTIN. An unknown product returns an error listing every valid slug.

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": {
      "product": "<product>"
    },
    "name": "routersua_get_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
productYesOne product: a slug from search results, a model code such as GL-MT6000 or GL-E750V2, a store code such as RUA-GL-MT6000, or a 13-digit GTIN; case does not matter.

Output Schema

NameRequiredDescriptionDefault
skuYes
urlYes
codeYes
gtinYes
nameYes
slugYes
imageYes
modelYes
imagesYes
ratingYes
on_saleYes
reviewsYes
summaryYes
cart_urlNo
categoryYes
price_uahYes
descriptionYes
availabilityYes
manufacturerYes
stock_statusYes
specificationsYes
regular_price_uahYes
backorder_ship_dateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that price and availability are read live, a photo is attached as an image, and cart_url opens checkout with one piece in the cart. It also describes the unknown-product error behavior, including that the error lists every valid slug.

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?

The description is front-loaded with the return behavior, followed by usage guidance and alternatives, then parameter and error details. Despite being dense, every clause contributes operationally useful information.

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?

For a one-parameter read tool with annotations and an output schema, the description covers the important gaps: return content, live pricing, image attachment, cart URL behavior, alternatives, identifier formats, and error behavior. Nothing needed to invoke the tool correctly is missing.

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 100%, and the description's explanation of accepted product identifiers largely repeats what the schema already documents. It adds no syntax or formatting detail beyond the slug, model code, store code, and GTIN information already present in the input schema.

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 states a specific verb and resource: return full details of one RoutersUA product. It also names the exact content returned (description, specifications, photos, price in UAH, availability, backorder ship date) and distinguishes this single-product tool from comparison and multi-item cart tools.

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?

It gives explicit when-to-use guidance: when the user names one product or after routersua_search_products. It also states when not to use this tool by routing two-or-more-product comparisons to routersua_compare_products and multi-product or multi-quantity carts to routersua_create_cart_link.

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