Skip to main content
Glama

PuntoSeguro · Seguros de vida y salud

Start a life-insurance application

start_life_insurance_application
Read-onlyIdempotent

Returns the secure link to start an application on puntoseguro.com for one quote, identified by an insurer id from list_life_insurance_quotes, a coverage option, the date of birth and the coverage amount. The application, health questionnaire and signature are completed by the user on puntoseguro.com; this tool submits nothing and collects no personal data. The final premium is subject to the insurer's underwriting.

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": {
      "insurer_id": "<insurer_id>",
      "birth_year": "<birth_year>",
      "birth_month": "<birth_month>",
      "birth_day": "<birth_day>",
      "coverage_amount_eur": "<coverage_amount_eur>"
    },
    "name": "start_life_insurance_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
birth_dayYesBirth day from 1 to 31
birth_yearYesFour-digit birth year
insurer_idYesInsurer id returned by list_life_insurance_quotes for the same date of birth and coverage amount
birth_monthYesBirth month from 1 to 12
coverage_variantNoCoverage option the user chose; death if the user has not chosen anotherdeath
coverage_amount_eurYesRequested life-insurance coverage amount in euros

Output Schema

NameRequiredDescriptionDefault
typeYes
insurer_idYes
insurer_nameYes
application_urlYes
coverage_variantYes
annual_premium_eurYes
coverage_amount_eurYesRequested life-insurance coverage amount in euros

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower; the description usefully adds that nothing is submitted and no personal data is collected, that the questionnaire and signature happen on puntoseguro.com, and that the final premium depends on underwriting. That is real side-effect and outcome context beyond the annotations, though link expiry or reuse behavior is not mentioned.

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?

Three sentences, front-loaded with the return value, followed by behavioral disclosure and the underwriting caveat. No sentence is redundant with the name, title, or schema.

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

Completeness4/5

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

For a six-parameter tool with a full output schema and annotations, the description covers prerequisites, side effects, and outcome uncertainty, which is close to complete. It stops short only on how it relates to the near-duplicate open_life_insurance_quote_form sibling.

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 ranges for birth_day/month/year and the enum for coverage_variant, so the schema already carries the semantics. The description only loosely restates that the quote is identified by insurer id, coverage option, date of birth and amount, adding no format or constraint detail beyond what is structured. 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?

States a specific verb and artifact ('Returns the secure link to start an application on puntoseguro.com') plus the exact inputs that identify the quote. It explicitly ties itself to the list_life_insurance_quotes output, so an agent can tell it apart from the listing/quote siblings without opening a schema.

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?

The description implies a clear prerequisite chain: the insurer_id must come from list_life_insurance_quotes 'for the same date of birth and coverage amount', so the agent knows this tool is a follow-up to quote discovery. It gives no explicit exclusions and never distinguishes itself from the very similarly named open_life_insurance_quote_form sibling, which is the main remaining ambiguity.

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