Skip to main content
Glama

Sigo Seguros car insurance quotes

Retired: the other carriers' questions

other_carrier_questions
Read-only

Retired. Do not call it: carrier_questions asks every carrier's questions at once, and get_quote carries the firm prices in firm_prices.

Kept so an older conversation that reaches it is told where to go, with the link. It asks nothing and reads nothing.

Input Schema

NameRequiredDescriptionDefault
localeYesThe language the customer is writing in. Set it from their own messages rather than leaving the default: the estimate's notice comes back in this language, and a notice the customer cannot read discloses nothing. Sigo serves these two languages only.
quote_idYesThe handle start_quote returned.
answers_so_farNoIgnored: nothing is carried here any more.

Output Schema

NameRequiredDescriptionDefault
noteYesWhat to do with these questions, in the customer's language.
preambleYesSigo's own words for the customer, to say as they are before the first question. Not one of the carrier's questions and not answered. Null when there is nothing to ask here.
next_stepYesWhere the customer finishes. Theirs at any point, not only at the end.
questionsYesIn the order the platform ranked them.
ask_togetherYesCodes that can be put to the customer in one turn, grouped the way the carrier groups them. Ask each block as one message and send its answers together. A question with `depends_on` is in no block: it gets its own turn, after the one it hangs off. Empty when there is nothing to ask here.
can_answer_hereYesAlways false: these questions are asked by carrier_questions now, once for every carrier.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / answers_so_far / description
      Previous value: -"The `answers_so_far` answer_carrier_questions handed back when the first option ended, when there was one: what the customer already answered is then not asked again."New value: +"Ignored: nothing is carried here any more."
    • changedOutput schema / properties / can_answer_here / description
      Previous value: -"False when there is nothing to ask here: nobody priced the customer, and a Sigo agent takes it."New value: +"Always false: these questions are asked by carrier_questions now, once for every carrier."
  2. Added
  3. Removed
  4. Added

TDQS

A3.9/5.0
Behavior1/5

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

Annotations declare openWorldHint=true, implying external interaction, while the description says it 'asks nothing and reads nothing' and is retired. That directly contradicts the openWorld annotation and conflicts with the read-only-operation implication; per the rubric, a contradiction scores 1.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

The text is very short and front-loads the critical instruction: 'Retired. Do not call it.' Every sentence serves the legacy-routing purpose with no waste.

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?

Given the retired status and the presence of an output schema, an agent only needs routing information. The description provides the alternatives and explains the legacy-conversation context, so nothing necessary is missing.

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%, including descriptions for quote_id, locale, and answers_so_far. The description adds no parameter meaning beyond noting that answers_so_far is ignored, which the schema already states, so the baseline 3 applies.

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 states the tool is retired and explicitly says 'Do not call it,' then identifies the intended alternatives: carrier_questions and get_quote. This clearly distinguishes it from siblings and tells an agent what the tool is and is not for.

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 gives explicit when-not-to-use guidance and names the replacement tools with their roles. An agent reaching this definition is told exactly where to go instead of invoking it.

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