Skip to main content
Glama

Quote an order

quote_order

Price new domains and mailboxes server-side. Creates a 15-minute quote; registers and charges nothing. Show human_summary to the user exactly before create_checkout. Ordering domains needs registrant with every one of: first_name, last_name, real_address, city, state_province, postal_code, country, phone, organization_name, job_title (email_address optional); collect them from the user upfront.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "quote_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainsNoNew root domains to register (check them with check_domains first).
personaNo
mailboxesNoTotal mailbox slots to add (a new subscription starts at 12). With new domains, mailboxes are created and spread over them, at most 10 per domain; slots beyond that stay paid and are filled when a domain is added (the quote's human_summary says so).
test_modeNoStripe test mode, nothing registered or charged. Not available in production.
registrantNoDomain registrant contact, required when domains are ordered. Ask the user for ALL of these before calling quote_order, in one question; never invent them: first_name, last_name, real_address (street), city, state_province, postal_code, country, phone (international format, e.g. +15125550100), organization_name, job_title. email_address is optional (defaults to the account email).
workspace_idNoWorkspace id. Optional: defaults to the workspace picked at sign-in or bound to the API key.
mailbox_domainsNoInstead of new domains: active domains the workspace already has (bought, or connected with connect_own_domains once list_domains shows dns_status active) to create the mailboxes on. Needs persona; no registrant.
redirect_domainNoWhere visitors of the new domains are redirected (usually the user's website).
mailboxes_per_domainNoAlternative to mailboxes: this many on each new domain (or on each mailbox_domains entry).

Output Schema

NameRequiredDescriptionDefault
kindNo
linesNo
linksYes
statusNo
domainsNo
currencyNo
quote_idNo
warningsNo
next_stepYesWhat to do next, in one sentence.
test_modeNo
expires_atNo
workspace_idNo
due_now_centsNo
human_summaryNo
monthly_centsNo
review_reasonNo
mailboxes_afterNo
mailboxes_beforeNo
mailbox_addressesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Adds meaningful behavior beyond the annotations: the quote expires in 15 minutes, nothing is registered or charged, and human_summary must be surfaced verbatim. It does not state that each call yields a distinct non-idempotent quote (consistent with idempotentHint=false), leaving that trait implicit.

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?

Three sentences, front-loaded with the pricing purpose and the no-charge guarantee before the more granular registrant requirement. The long field enumeration slightly duplicates the schema, but it earns its place by emphasizing the collection requirement.

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 9-parameter tool with nested objects, output schema, and annotations, the description covers the main workflow, the side-effect profile, and the critical precondition. Remaining gaps (pricing/currency behavior, non-idempotency) are largely covered by the output schema or annotations.

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 already 89%, so the baseline is 3. The description goes further by making the registrant block a hard precondition for domain orders, enumerating its required fields, marking email_address optional, and instructing that values be collected from the user in one question rather than invented.

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 ('Price new domains and mailboxes server-side') plus the artifact produced ('Creates a 15-minute quote'). It also distinguishes itself from create_checkout and implies the check_domains prerequisite, so an agent can place it correctly among siblings.

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 a clear workflow contract: show human_summary before calling create_checkout, and collect registrant data upfront rather than mid-quote. It names the downstream sibling but stops short of explicit when-not-to-use conditions or the check_domains-first rule (that lives only in the schema).

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