Skip to main content
Glama

Airsockfly

Get travel insurance quotes

search_insurance
Read-onlyIdempotent

Get travel insurance quotes for a trip: destination, dates and the age of every insured person. Premiums are calculated by the server.

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": {
      "destination": "<destination>",
      "startDate": "<startDate>",
      "endDate": "<endDate>",
      "travellerAges": "<travellerAges>"
    },
    "name": "search_insurance"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoInsurance type.
limitNoMaximum number of offers to return, from 1 to 30. Default 10.
endDateYesEnd date, YYYY-MM-DD.
startDateYesStart date, YYYY-MM-DD.
destinationYesDestination country or region of the trip.
travellerAgesYesAge of every insured person.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint and idempotentHint, so the safety profile is covered. The description's one added behavioral fact — 'Premiums are calculated by the server' — is genuinely useful because it tells the agent not to compute or estimate pricing, but it says nothing about quote validity, whether results are live or cached, or whether offers are subsequently bookable.

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?

Two sentences with no filler: the first front-loads the required inputs, the second carries the only behavioral note. Nothing is redundant and nothing needs reordering.

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?

For a six-parameter search tool with no output schema, the description is adequate but leaves the agent guessing about the result shape (per-offer premium, coverage details, number of offers) and about what to do next once quotes are returned. Annotations cover the read-only, open-world nature, which limits how much the description must carry.

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%, so all six parameters are already documented, including enum values for type and the 1–30 range for limit. The description only restates destination, dates and ages and never mentions type or limit, so it adds no meaning beyond the schema; baseline 3 applies.

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?

The description names a specific verb and resource ('Get travel insurance quotes') and lists the identifying trip inputs, which cleanly separates it from search_flights, search_hotels and other siblings. It slightly undersells scope: the schema's enum allows medical, cancellation, luggage and sport coverage, but the description only says 'travel insurance quotes'.

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?

There is no explicit when-to-use or when-not-to-use guidance and no routing to alternatives (e.g., that create_booking or get_offer handle booking a specific offer afterward). The phrase 'for a trip' implies context but states no prerequisites or exclusions.

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