Skip to main content
Glama

Create a RoutersUA cart link

routersua_create_cart_link
Read-onlyIdempotent

Create a link that opens the RoutersUA checkout with the chosen products and quantities in the cart, at live prices in UAH, for the user to open, review and complete on the site. Use it when the user is ready to buy or wants several products in one cart; identify products with routersua_search_products first, and for a single piece of one product the cart_url of routersua_get_product is enough. Nothing is ordered, reserved or paid here. Repeated products are added together (at most 99 each); products that cannot be ordered now are left out and listed in unavailable; products on backorder are included and marked with their ship date; an unknown product, or none orderable, returns an error.

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": {
      "items": "<items>"
    },
    "name": "routersua_create_cart_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesOne to ten products, e.g. [{"product": "GL-MT6000", "quantity": 2}, {"product": "GL-E750V2"}].

Output Schema

NameRequiredDescriptionDefault
urlYes
linesYes
currencyYes
unavailableYes
goods_total_uahYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare readOnlyHint/idempotentHint true and destructiveHint false, and the description reinforces this with "Nothing is ordered, reserved or paid here." Beyond that it discloses non-obvious behavior the annotations cannot convey: duplicates are summed (capped at 99), unorderable products are omitted and reported in `unavailable`, backordered items are included with a ship date, and unknown or wholly unorderable input returns an error.

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?

It is front-loaded with purpose, then usage, then behavioral caveats, and no clause is filler. The final semicolon-chained sentence is dense and could be split into a short bulleted set of edge-case rules for easier scanning, which keeps it just short of top marks.

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?

An output schema exists, so return values need not be spelled out, yet the description still names the `unavailable` field and the error condition. Combined with the aggregation cap, backorder handling, and the no-order/no-payment guarantee, an agent has everything needed to call this correctly and set user expectations.

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 100% and the schema already documents slug/model/store code/GTIN and the 1-99 quantity range, so the baseline would be 3. The description adds real meaning beyond that: repeated entries are aggregated rather than duplicated, and per-item outcomes (omitted vs. backordered with ship date) determine what the agent should expect back from the items it passes.

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 uses a specific verb and resource ("Create a link that opens the RoutersUA checkout with the chosen products and quantities in the cart") and states the pricing/currency scope (live prices in UAH). It also distinguishes itself from siblings by name, pointing to routersua_search_products for identification and routersua_get_product's cart_url for single-item cases.

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 an explicit trigger ("when the user is ready to buy or wants several products in one cart") and an explicit exclusion with the alternative to use instead ("for a single piece of one product the cart_url of routersua_get_product is enough"). It also states a prerequisite step: identify products with routersua_search_products first.

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