Assurs LAMal comparator

Prepare an optional adviser link

create_adviser_handoff_link

Read-onlyIdempotent

Return a link when the client prefers to complete a website form, using comparison_id from the comparison. No contact details, lead or email are sent. When the web form is disabled the server answers 503 adviser_unavailable: offer contact@sp-insurance.ch instead. For a client who asks you to send the request in this conversation, use request_adviser_contact after explicit consent instead. Swiss Premium Insurance assistance is optional; clients may apply directly with insurers.

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": {
      "comparison_id": "<comparison_id>"
    },
    "name": "create_adviser_handoff_link"
  }
}

Input Schema

Name	Required	Description
`agent`	No
`agentContext`	No	Deprecated alias of agent; not with agent.
`comparison_id`	Yes

Output Schema

Name	Required	Description	Default
`status`	No
`expires_at`	No
`handoff_url`	Yes
`submits_lead`	Yes
`transmits_contact_data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 25, 2026

addedInput schema / properties / agent / properties / kind / description

Added value: +"Optional. Accepted values: personal_assistant, conversational_assistant, coding_agent (personal_agent and chat_assistant are read as personal_assistant and conversational_assistant)."

addedInput schema / properties / agentContext / properties / kind / description

Added value: +"Optional. Accepted values: personal_assistant, conversational_assistant, coding_agent (personal_agent and chat_assistant are read as personal_assistant and conversational_assistant)."

First observedOct 24, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover the read-only/idempotent safety profile, and the description layers on substantive context they cannot express: no contact details, leads or emails are transmitted, the specific 503 adviser_unavailable error and its human fallback, and the fact that the service is optional. That is exactly the operational context an agent needs before proposing the link.

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 primary behavior in the first sentence, then spends the remaining sentences on privacy, error handling, the alternative tool and optionality — each carrying distinct information. It is dense but nearly every clause earns its place.

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?

Output schema exists, so the return value needs no explanation. Given the tool's complexity (nested agent metadata, deprecated alias, a possible 503), the description supplies the consent boundary, the alternate-tool routing and the degradation path, leaving nothing critical unresolved for a correct invocation.

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 only 33%, and the description addresses just comparison_id, clarifying its provenance ('from the comparison') without giving format details. The large nested agent/agentContext objects are not mentioned at all in the description, though the schema's own sub-property descriptions carry most of that load, so the gap is mitigated rather than eliminated.

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?

States a specific verb and resource ('Return a link' for a website form handoff) and ties it to the required input ('using comparison_id from the comparison'). It is clearly distinguishable from the sibling request_adviser_contact, which it explicitly names as a different path.

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 explicit conditions: use when the client prefers the website form; use request_adviser_contact (after explicit consent) when the client wants the request sent in-conversation. It also pre-empts the failure path (web form disabled → 503 → offer contact@sp-insurance.ch) so the agent knows what to do without improvising.

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

All Assurs LAMal comparator 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?