Sigo Seguros car insurance quotes

Read a Sigo link the customer already has

resolve_application_link

Read-only

Outside the three steps: for a customer who arrives with a Sigo link they already have.

Says what a Sigo link points at, how far that application has got, and the one thing the customer has to do next. Call it when someone shows up with a link — from an email, a text, or their own notes — and asks for help finishing.

Pass what they wrote, as they wrote it. It resolves the short link, the long one and a bare code, with surrounding words and punctuation.

It reads only: it opens nothing on the customer's behalf, and asking twice changes nothing. It reports no price, carrier or personal detail, because Sigo does not send any — whoever holds a link gets this same answer, so there is nothing here that identifies its owner. Say the message as given rather than composing one.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`locale`	Yes	The 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.
`pasted_link`	Yes	The link or code the customer gave, exactly as they wrote it — surrounding words and punctuation are fine. Do not clean it up or guess at a link the customer did not provide.

Output Schema

TableJSON Schema

Name	Required	Description
`url`	Yes	The link to hand back so the customer can continue, or null when nothing resolved. Use this URL rather than the one the customer pasted.
`state`	Yes	How far the application has got. Coarse on purpose.
`message`	Yes	What to tell the customer, already written in their language. Say this rather than composing your own: it is the only description of the application Sigo has checked, and it deliberately states no price, carrier or personal detail because none was read.
`next_step`	Yes	The single next action, as a value. `message` is the wording for it.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 28, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint. The description adds real behavioral context beyond them: idempotence ('asking twice changes nothing'), no side effects ('opens nothing on the customer's behalf'), and a disclosure posture ('reports no price, carrier or personal detail... nothing here that identifies its owner'), which tells the agent not to expect personalized or sensitive output.

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?

Core behaviour and the trigger are front-loaded, and every sentence carries information. It is slightly dense and the opening sentence is a fragment that requires reading on to parse, keeping it just short of a 5.

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?

An output schema exists so return values need not be described, yet the description still states what the answer contains and the disclosure constraints. With only two fully-documented params and annotations covering safety, nothing an agent needs to call this correctly is missing.

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 100%, so the baseline is 3, but the description adds accepted-format semantics the schema does not: it resolves short links, long links and bare codes, tolerates surrounding words and punctuation, and must be passed verbatim. That is genuine value over the schema text.

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?

Specific verb+resource: it says what a Sigo link points at, how far the application has progressed, and the next required customer action. It also explicitly positions itself against the sibling flow ('Outside the three steps'), so an agent can distinguish it from start_quote/next_question/get_quote without reading schemas.

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 a concrete trigger condition ('Call it when someone shows up with a link — from an email, a text, or their own notes — and asks for help finishing') and names the alternative path (the three-step flow) it sits outside of. Routing is unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Sigo Seguros car insurance quotes tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?