Skip to main content
Glama

moltbound_quick_quote

One-shot quotes across any service. Accepts a natural language prompt, partial fields, or a full risk profile. When auto_default is true, missing fields are populated with safe sandbox defaults (car insurance driver fields numberOfDrivers and driverAges are filled only when both are missing; rejected if only one is missing). Pass grant_token for Protected Mode. NEXT STEP after quotes: nothing is bought until a person approves. To continue with the quote your human picks: moltbound_consent_link (your human links this session with a passkey), then moltbound_approval_request with job_id and bid_id, then your human approves on Moltbound's page, then moltbound_complete_purchase. Every quote reply also has a next_step object with these calls filled in. No human available? Test it with moltbound_human_sim_start. SANDBOX: use fictitious data only. Do not enter real personal details.

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

Input Schema

NameRequiredDescriptionDefault
stateNoTwo-letter US state code, e.g. TX
promptNoPlain-language request, e.g. 'car insurance for a 2019 Honda Civic in Austin TX 78701'. No names or ID numbers.
service_idNoWhich of the 20 US services to quote, e.g. car_insurance, home_building, dog_pet_insurance, travel, electricity.
grant_tokenNoOptional grant token for Protected Mode
auto_defaultNoSet true to fill missing fields with safe sandbox defaults. Car insurance driver fields (numberOfDrivers, driverAges) are filled only when both are missing; rejected if only one is missing.
risk_profileNoOptional: the service's fields as key/value pairs (see moltbound_requirements). They may also be passed at the top level.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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 disclosure burden and does so well: it states the sandbox constraint and fictitious-data requirement, the Protected Mode token requirement, the auto-default fill rule including the exact rejection condition when only one of numberOfDrivers/driverAges is present, and that replies carry a next_step object. It also discloses a critical side-effect boundary — no purchase occurs without human approval — which is exactly the kind of behavior an agent must know before calling.

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 the auto_default rule, then the workflow, then the sandbox warning — a sensible ordering. It is dense but almost every sentence is actionable; the only waste is the verbatim duplication of the auto_default and sandbox text already present in the schema, and the first sentence's slightly clipped 'One-shot quotes across any service.'

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 six-parameter tool with a free-form nested risk_profile, no output schema, and no annotations, the description covers input modes, defaults, security token, side effects, and follow-on calls. It stops short of describing what a quote reply actually contains beyond the next_step object (price fields, quote id, expiry), which would matter since no output schema exists.

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 baseline is 3. The description restates rather than extends the schema: the auto_default car-insurance edge case appears verbatim in the schema, and grant_token's 'Protected Mode' purpose is also already there. It does add the framing that fields may arrive via prompt, top-level partials, or risk_profile, but that relationship is largely spelled out in the schema description too.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ('One-shot quotes across any service') and enumerates the three accepted input shapes (natural-language prompt, partial fields, full risk profile). It is clear what the tool does, but it never distinguishes itself from the similarly named sibling moltbound_get_quotes or explains why one would quote here rather than fetch existing quotes there.

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?

Usage context is unusually explicit: it warns 'nothing is bought until a person approves' and lays out the exact follow-on chain (consent_link → approval_request → human approves → complete_purchase), plus a fallback ('No human available? Test it with moltbound_human_sim_start'). The gap is that it gives no when-not-to-use guidance relative to moltbound_get_quotes, moltbound_quote_status, or moltbound_requirements, which an agent choosing among 17 siblings would want.

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