Skip to main content
Glama

moltbound_get_quotes

Request simulated quotes (cheapest first) with the human's answers. Pass parameters directly for any of the 20 services. 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

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": {
      "session_token": "<session_token>",
      "service_id": "<service_id>"
    },
    "name": "moltbound_get_quotes"
  }
}

Input Schema

NameRequiredDescriptionDefault
service_idYesWhich of the 20 US services to quote, e.g. car_insurance, home_building, dog_pet_insurance, travel, electricity.
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_profileNoThe service's fields as key/value pairs (see moltbound_requirements). They may also be passed at the top level.
session_tokenYesSession token from moltbound_start_session

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 burden and does it well: it discloses that quotes are simulated, that nothing is purchased until a person approves, that every reply contains a next_step object with the follow-on calls pre-filled, and that the environment is a sandbox requiring fictitious data. This is the safety and lifecycle context an agent needs 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-loads the purpose then the workflow in a single directional block, with the sandbox warning last. It is dense but nearly every clause earns its place; the sentence noting that the reply repeats the same calls in a next_step object is mildly redundant with the chain already spelled out.

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?

There is no output schema, and the description compensates by describing the return (quotes ordered cheapest first, plus a next_step object). Combined with the end-to-end purchase chain and the sandbox constraint, an agent has everything needed to call this and handle the result correctly.

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 documents service_id's enum, auto_default's fill rules, risk_profile, and session_token. The description adds only the note that parameters can be 'passed directly for any of the 20 services', which largely duplicates what risk_profile's own description and additionalProperties already convey. Baseline 3 applies.

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?

States a specific verb and resource ('request simulated quotes'), the ordering semantics ('cheapest first'), and the scope ('any of the 20 services'). It does not distinguish itself from the sibling moltbound_quick_quote, so an agent cannot tell from this text alone which quoting tool to pick.

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 an unusually explicit follow-up path: consent_link, then approval_request with job_id and bid_id, then human approval, then complete_purchase, plus a fallback to moltbound_human_sim_start when no human is available. It also routes to moltbound_requirements for field definitions. The only gap is the unmentioned quick_quote alternative.

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