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 only the Sigo link or code they shared. It resolves the short link, the long one and a bare code.

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

Name	Required	Description	Default
`locale`	No	The language to write the returned `message` in: the customer's own, es or en.	es
`pasted_link`	Yes	Only the Sigo link or code the customer shared (a sigoseguros.com link or a short code), not the rest of their message. Stray punctuation around it is fine; do not guess at a link the customer did not provide.

Output 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.

Changed5 schema fields changedSep 30, 2026

addedInput schema / properties / locale / default
```
Added value: +"es"
```

changedInput schema / properties / locale / description

Previous value: -"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."New value: +"The language to write the returned `message` in: the customer's own, es or en."

changedInput schema / properties / pasted_link / description

Previous value: -"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."New value: +"Only the Sigo link or code the customer shared (a sigoseguros.com link or a short code), not the rest of their message. Stray punctuation around it is fine; do not guess at a link the customer did not provide."

changedInput schema / properties / pasted_link / maxLength
```
Previous value: -2048New value: +512
```

changedInput schema / required

Previous value: -[
-  "pasted_link",
-  "locale"
-]New value: +[
+  "pasted_link"
+]

First observedSep 28, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond readOnlyHint/destructiveHint it discloses that the call is idempotent ('asking twice changes nothing'), that it takes no action on the customer's behalf, and, without being asked, that no price, carrier or personal detail is returned because any link holder gets the same answer. That is genuinely useful behavioral context an agent could not infer from annotations.

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?

The purpose is front-loaded in the first sentence and each subsequent sentence carries distinct information (trigger, input, safety, output guidance). It is moderately long and slightly conversational, but no sentence is filler.

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?

With an output schema present, the description need not explain return values, and it covers the trigger, input format, and safety posture. Nothing an agent needs to call this correctly appears to be 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 real meaning: it clarifies what to pass (only the link or bare code, not the surrounding message) and which formats are accepted (short link, long link, bare code). The locale parameter is left to the schema.

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 a specific verb and resource — it resolves a pasted Sigo link and reports what it points at, how far the application has progressed, and the next step. It positions itself against the sibling quote-flow tools with 'Outside the three steps', so an agent can distinguish it from start_quote/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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit trigger: call it when a customer arrives with a link from an email, text, or notes and asks for help finishing. It also implicitly excludes the three-step flow. It stops short of naming a specific sibling tool as the alternative, so it is clear but not fully routing.

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?