Skip to main content
Glama

Create a cart link

create_cart_link
Read-only

Make a link that opens the store's cart with these products already in it. The customer opens it, checks the cart and completes the order on the site. Nothing is ordered until they confirm there.

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

Input Schema

NameRequiredDescriptionDefault
itemsYes
currencyNoAlso show prices in this currency (USD, EUR, GBP, RUB); approximate, at today's rate. Payment is in EGP. Default EGP only.
languageNoLanguage of the answer: en, ar, ru, it or de. Default en.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / currency
      Added value: +{
      +  "description": "Also show prices in this currency (USD, EUR, GBP, RUB); approximate, at today's rate. Payment is in EGP. Default EGP only.",
      +  "enum": [
      +    "USD",
      +    "EUR",
      +    "EGP",
      +    "RUB",
      +    "GBP"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false; the description reinforces this by explicitly stating 'Nothing is ordered until they confirm there,' resolving the key agent worry that creating a cart might transact. It omits link lifetime/expiry and whether the link is reusable, which would be useful secondary detail.

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?

Three short sentences: capability first, then customer workflow, then the safety-relevant guarantee. No filler, and the most important constraint is placed last for emphasis.

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?

For a low-complexity, single-purpose tool with no output schema, the description covers what the tool produces at a conceptual level. It could say what the returned link looks like or whether it expires, but nothing essential to invoking it 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 67% — currency and language are documented in the schema, while the items array carries no description and its per-item quantity cap and 30-item limit are visible only as constraints. The description adds only that products go 'already in' the cart, so it roughly matches schema-level information rather than extending 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?

Specific verb and resource: 'Make a link that opens the store's cart with these products already in it.' This is a distinct capability from browsing/searching products, and the second sentence clarifies the deliverable is a hand-off link, not an order.

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?

Gives clear context for use: pre-fill a cart for a customer who then reviews and completes the order on the site. It does not state when-not to use it or name an alternative, but the workflow framing makes the intended scenario unambiguous.

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