Skip to main content
Glama

moltbound_quote_status

Poll a quote job until complete, then show the human the quotes. Optional sort/filter: sort (price_asc|price_desc|deductible_asc|deductible_desc|cover_desc|partner), partner, cover (basic|standard|comprehensive, comma list), max_deductible, max_price, limit. The human picks which quote to continue with. 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>",
      "job_id": "<job_id>"
    },
    "name": "moltbound_quote_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNo
coverNo
limitNo
job_idYes
partnerNo
max_priceNo
session_tokenYesFrom moltbound_start_session, moltbound_human_sim_headless or moltbound_human_sim_verify
max_deductibleNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / session_token / description
      Previous value: -"From moltbound_start_session or moltbound_human_sim_verify"New value: +"From moltbound_start_session, moltbound_human_sim_headless or moltbound_human_sim_verify"
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does well: it discloses that this is a blocking poll-until-complete operation, that a human selects the quote, that every quote reply embeds a next_step object, and that only fictitious data may be used in the sandbox. It does not cover timeout, failure, or partial-result behavior, 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first sentence, and the remaining sentences handle sorting, human selection and the approval chain in that order. It is dense but nearly every clause carries information; the flow description could be tightened.

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 an eight-parameter, multi-step purchase-funnel tool with no output schema and no annotations, the description covers routing, human handoff, the next_step payload and the sandbox safety constraint. Remaining gaps are operational details such as poll duration and error handling.

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 only 13% and the schema declares no enums, so the description compensates materially by enumerating the sort values (price_asc through partner) and the cover values (basic|standard|comprehensive, comma list) plus max_deductible, max_price and limit. partner and limit get no explanation of format or effect, leaving a small residual gap.

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: poll a quote job to completion, then present the quotes to a human. It is concrete enough to distinguish from a plain fetch, but it never names moltbound_get_quotes or clarifies how polling differs from a one-shot retrieval, so the agent must infer that boundary.

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?

Gives an explicit when-to-use path plus the full downstream sequence: consent_link, approval_request, human approval, then complete_purchase. It also names a fallback (moltbound_human_sim_start) when no human is available and states that nothing is purchased until a person approves.

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