Skip to main content
Glama
Sign In

AssurancesLabs

by com.assuranceslabs
OverviewDiscussionsAdmin

resolve_quote_intent

Read-onlyIdempotent

Maps an insurance type to the canonical questionnaire deep link and required fields (same as POST /api/ai/quote-intent).

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": {
      "insurance_type": "<insurance_type>"
    },
    "name": "resolve_quote_intent"
  }
}

Input Schema

NameRequiredDescriptionDefault
intentNoOptional intent hint for the agent
insurance_typeYesOne of the 21 funnels: habitation, pno, loyers-impayes, decennale, auto, moto, mobilite-douce, sante, prevoyance, vie, gav, scolaire, obseques, dependance, voyage, animaux, protection-juridique, emprunteur, rc-pro, cyber, multirisque-pro. French labels, English names and the vertical slugs of list_insurers (rc_pro, gli, protection_juridique…) are accepted as aliases.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is covered. The description adds that the result includes a deep link and required fields, which is real value, but it says nothing about failure behavior for unknown or alias-ambiguous insurance types.

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?

A single front-loaded sentence with no filler. The parenthetical API reference is slightly cryptic for an agent that cannot call that endpoint, but it costs little space.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the burden of describing returns, and it only names two result elements without structure or shape. For a two-parameter read-only mapping tool that is borderline adequate but leaves the response format underspecified.

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 coverage is 100% and the insurance_type description already enumerates all 21 funnels and the alias rules, so the description adds nothing beyond the schema. Baseline 3 applies; the 'intent' hint parameter is not addressed at all in the description.

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 ('Maps') and resource ('an insurance type to the canonical questionnaire deep link and required fields'), so the transformation is unambiguous. It does not differentiate from the only sibling, get_ai_sources, but that sibling appears unrelated enough that confusion risk is low.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No guidance on when to call this versus other tools, no prerequisites, and no note on what to do when the insurance type is unrecognized. The parenthetical API equivalence is context, not usage guidance.

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

All AssurancesLabs toolsInspect
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