Skip to main content
Glama

Request a formal quote

request_quote

Use it only after the person chose one or more yachts from a search_yachts, best_deals or get_yacht answer, gave their days and party, and said yes to a written quote: ask them before you call it. Pass the page links exactly as those answers returned them, the days, the party and anything they want the desk to know, in their words. The desk sends a formal quote in writing, with every cost on it, to the person's own email or phone; this answer only says it was received and where the quote goes. Nothing is booked or paid: the person confirms the booking with the desk. Arguments: email, phone, session, name, items, from, to, party, notes. Any other name is refused.

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

Input Schema

NameRequiredDescriptionDefault
toNoCheck-out day, YYYY-MM-DD.
fromNoCheck-in day, YYYY-MM-DD.
nameNoOptional: the person's name, as they gave it.
emailNoThe person's own email, as they gave it: the quote is sent there. This, phone or session is needed.
itemsYesThe yacht page links to quote (absolute URLs on this site), exactly as a search, best_deals or get returned them. At most 20.
notesNoWhat the person wants the desk to know, in their words (at most 2000 characters).
partyNoHow many people.
phoneNoThe person's own phone, international form (+ and country code), as they gave it. This, email or session is needed.
sessionNoThe session an earlier request_quote answer returned. Pass it instead of email or phone.

Output Schema

NameRequiredDescriptionDefault
statusYesreceived: the desk has the request; already_received: this session asked the same in the last day.
sessionNoOnly on the call that created the contact: pass it from then on.
nextStepYesWhere the written quote goes, in words to tell the person.
enquiryRefNoThe request's reference, returned once.
sessionExpiresAtNoWhen that session stops working, ISO time.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / session / description
      Previous value: -"The session an earlier answer returned. Pass it instead of email or phone."New value: +"The session an earlier request_quote answer returned. Pass it instead of email or phone."
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations declare openWorldHint and non-idempotent, non-destructive, non-readonly behavior; the description adds substantial context beyond that — that the item links must be passed verbatim, that nothing is booked or paid, and that the response only confirms receipt and the destination. It stops short of saying what happens on a repeat call (duplicate quote?) or any rate limits, which matters for a non-idempotent outbound action.

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 the gating condition, then mechanics, then the argument list — a logical order. The enumeration of all nine argument names largely repeats the schema, but the accompanying 'any other name is refused' makes it earn partial keep; the prose is dense but not padded.

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?

For a 9-parameter write-style tool with a full schema and an output schema, the description covers the prerequisites, the handling of items and contact details, the downstream deliverable, and the limits of the response. Nothing an agent needs in order to call it correctly is missing.

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 100%, so the baseline is 3, but the description adds real meaning: items must be page links exactly as the earlier answers returned them, the day/party fields come from what the person stated, notes are in the person's own words, and the closed argument set is enforced ('any other name is refused'), reinforcing additionalProperties=false.

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 names the concrete effect — the desk sends a formal written quote with every cost to the person's own email or phone — and distinguishes this tool from the discovery siblings by requiring items that came from search_yachts, best_deals or get_yacht. An agent can tell this is the terminal conversion step, not another search.

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 spells out explicit preconditions: person must have chosen yachts from a prior search/deals/get answer, given days and party, and said yes to a written quote — plus an instruction to ask before calling. It also states what the tool is NOT (a booking or payment), routing confirmation to the desk instead.

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