Skip to main content
Glama

Virág — Manhattan flower delivery

Create a flower order

create_order

Create an order and get a secure Stripe checkout_url. The order is confirmed only after payment at checkout_url (pay it yourself if you are able to complete a card checkout for your user, otherwise give the link to your user). Always confirm tier, total price, recipient, address, date and card text with the user first. Reuse idempotency_key on retries.

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": {
      "tier": "<tier>",
      "recipient_name": "<recipient_name>",
      "recipient_phone": "<recipient_phone>",
      "address_line1": "<address_line1>",
      "zip": "<zip>",
      "sender_name": "<sender_name>"
    },
    "name": "create_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipYes5-digit Manhattan ZIP code (10001–10282).
tierYesWhich bouquet: sweet ($119), romantic ($229) or grand ($749). All prices include card, delivery and tax.
agent_nameNoOptional: name of the AI agent/app placing the order (helps us support you).
buyer_emailNoBuyer's email for the receipt and delivery confirmation.
sender_nameYesHow the card is signed, e.g. 'Love, Daniel'.
card_messageNoText handwritten on the card, max 300 characters.
address_line1YesStreet address in Manhattan, e.g. '245 E 19th St'.
address_line2NoApartment, floor, company or suite.
delivery_dateNoYYYY-MM-DD in New York time. Omit for the earliest available date.
recipient_nameYesFull name of the person receiving the flowers.
idempotency_keyNoOptional: reuse the same key when retrying so the order is never created twice.
recipient_phoneYesRecipient's US phone number. The courier calls it for building access.
delivery_instructionsNoDoorman, buzzer code, 'leave with front desk', etc.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses that the order is not confirmed until payment, that a checkout_url is returned, that the agent may complete the card checkout itself, and that idempotency_key must be reused on retries. It omits failure modes such as link expiry, unavailable dates, or declined payments, which keeps it short of a 5.

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 tight sentences with the action and payoff front-loaded, followed by the confirmation prerequisite and the retry rule. Nothing is redundant and every sentence carries distinct information.

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 13-parameter mutation with no output schema and no annotations, the description supplies the essential return value (checkout_url) and the confirmation state, and the schema fully documents the inputs. It stops short of covering error or availability handling, which an agent would likely need on a failed attempt.

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%, so the schema already defines tier prices, ZIP constraints and idempotency semantics; the baseline is 3. The description reinforces which fields need user confirmation (tier, price, recipient, address, date, card text) and the retry key, but adds no meaning beyond the structured fields.

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 resource ('Create an order') plus the concrete outcome ('get a secure Stripe checkout_url') and the confirmation condition. An agent can distinguish this immediately from get_order_status or list_bouquets.

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 operational context: confirm tier, total, recipient, address, date and card text with the user first, and either complete the card checkout or hand the link to the user. It does not explicitly name alternatives (e.g., list_bouquets for tier selection or check_delivery for date availability), but the when-to-call condition is 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.