Skip to main content
Glama

Create a shareable quote

create_quote_link

Make a shareable quote page for the customer, with no side effects: no order, no email, no payment link and no stock hold. Each blind is priced and stock-checked now; the page shows the lines and total and its button fills the customer's cart and opens checkout, where prices are checked again. Valid 7 days. Use this when the customer wants to review, share or pay later, instead of create_checkout.

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_quote_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesConfigured blinds; validate colours with configure_product first

Output Schema

NameRequiredDescriptionDefault
noteYes
itemsYes
currencyYes
deliveryNo
quote_idYes
quote_urlYes
total_zarYes
expires_atYes
item_countYes
side_effectsYes
vat_includedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior3/5

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

Adds substantial context beyond annotations: no side effects (no order/email/payment link/stock hold), prices and stock locked in at creation but re-checked at checkout, and a 7-day validity window. However, the description does not reconcile the 'no side effects' framing with readOnlyHint=false on a tool that persists a new quote resource, nor does it say whether repeated calls produce duplicate links or how the page is addressed/returned. With annotations already covering the safety profile, this is good but not complete.

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?

Front-loaded with purpose then side-effect exclusions, and every clause carries information. The middle sentence is long and run-on (page rendering, cart-fill button, and re-check all in one breath), which slightly hurts scanability.

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?

An output schema exists and the single input parameter is fully documented, so return values need no explanation. What remains thin is the lifecycle edge cases of the created link (expiry handling, regeneration, duplicate calls) given this is a write operation with readOnlyHint=false.

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 nested item schema already documents colour, mount_type, no_drill, quantity and the ignored price fields, so the baseline of 3 applies. The description adds only the pricing/stock-check timing per blind, not parameter-level meaning beyond the 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?

States a specific verb and artifact ('Make a shareable quote page for the customer') and immediately scopes what it is not: no order, no email, no payment link, no stock hold. The agent can distinguish it from create_checkout without opening either schema.

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?

Explicit routing: 'Use this when the customer wants to review, share or pay later, instead of create_checkout.' Both the selecting condition and the named alternative are given, leaving nothing to inference.

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