Skip to main content
Glama

The Builders Supply catalog

Prepare product links for ordering

cart_link
Read-onlyIdempotent

Prepares ordering for chosen items: one product page link per item, the quantity rules and whether the published count covers the quantity. It does NOT fill a cart (prefilled_cart is always false): the customer opens the link, enters the quantity and checks out on the store site. This server takes no orders and no payment data.

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": "cart_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesitems as SKU and quantity

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds meaningful context beyond them: prefilled_cart is always false, the customer must open the link and enter quantity on the store site, and the server handles no order or payment data — the crucial handoff boundary an agent needs to avoid overpromising.

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, front-loaded with the deliverable and followed by the cart caveat and the no-orders/no-payment disclaimer. The final sentence slightly restates the cart point, but each clause carries an operational constraint, so waste is minimal.

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?

The output schema covers return values, so the description does not need to enumerate them, yet it still names the key artifacts (link, quantity rules, coverage flag). Combined with the explicit statement of what the server will not do, an agent has everything needed to call this correctly and set expectations.

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?

With a single parameter and 100% schema description coverage, the schema already carries the SKU/quantity semantics. The description adds only light meaning — that a quantity rule and a published-count coverage check accompany each item — without explaining formats, limits, or how quantity is validated, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 ('Prepares ordering for chosen items') and immediately concretizes the output as 'one product page link per item, the quantity rules and whether the published count covers the quantity.' It also marks its boundary with a cart-filling tool, though it never names any sibling, so differentiation rests on the negative statement rather than on routing.

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?

'Prepares ordering for chosen items' implies the context (a customer who wants to buy specific SKUs), and the closing sentences effectively state when this is NOT appropriate — no cart filling, no orders, no payment. However, there is no explicit guidance pointing to alternatives such as get_product or check_availability for discovery or availability checks, so usage is implied rather than directed.

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