Skip to main content
Glama

Zoya.bg

prepare_cart_link

BG/EUR pilot: preview selected explicitly selected exact product IDs and integer quantities (1..20). Members: merge selected items into the ONE active shared cart and preview ALL its items. Never drop earlier selections. Guests: standalone preview only; no persistent shared cart. Return a native Zoya cart link; NEVER open/fetch it automatically. Ask the customer to review and click. The preview page dispatches only once after confirmation. Completion at Zoya is not verified. No order/payment or stock reservation. Use already selected IDs; do not scan products or call merely to display search results.

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

Input Schema

NameRequiredDescriptionDefault
itemsYes
languageNobg

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?

With no annotations supplied, the description carries the full behavioral burden and does so: merge semantics that never drop earlier selections, guests get no persistent cart, the preview page dispatches only once after confirmation, Zoya completion is unverified, and there is no order, payment, or stock reservation. It also forbids auto-opening or fetching the returned link, which is a critical safety constraint.

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?

The content is front-loaded by audience (BG/EUR pilot, members, guests) and each line adds a distinct rule. Some phrasing is redundant, notably 'preview selected explicitly selected exact product IDs', which could be tightened, but there is no filler.

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 two-parameter tool with no output schema, the description covers mode-specific behavior, the returned link, and the lifecycle limits after handoff. The remaining shortfall is item object shape and the undocumented language parameter, which matter because the schema is entirely undescribed.

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 0%, so the description must compensate, and it partly does by specifying that items are exact product IDs with integer quantities bounded 1..20. It does not name the item object's field keys (additionalProperties is open) or mention the language parameter or its 'bg' default, leaving a gap an agent must guess at.

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 action (prepare a cart link), the exact inputs (explicitly selected product IDs plus integer quantities 1..20), and the output (a native Zoya cart link). It also distinguishes its role from browsing tools by saying not to call it merely to display search results or scan products.

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 ('Use already selected IDs') and when-not ('do not scan products or call merely to display search results'), and separates the two operating modes: members merge into the one active shared cart while guests get a standalone preview. The instruction to ask the customer to review and click before proceeding further clarifies the handoff.

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