travel-insurance
Server Details
Compare travel insurance quotes from 15+ insurers — Schengen, WHV, students, long stays, seniors.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 3.6/5 across 1 of 1 tools scored.
With only one tool, there is no risk of ambiguity or confusion between tools. The tool's purpose is clearly described.
A single tool named 'get_quote' is self-consistent. The verb_noun pattern is clear and appropriate.
Having only one tool for a travel insurance domain is too few. Typical insurance workflows require multiple operations such as getting quotes, managing policies, and handling claims, which are missing.
The tool only covers quote creation and subscription. Missing essential lifecycle operations like viewing existing subscriptions, updating, or cancelling leaves significant gaps for an agent.
Available Tools
1 toolget_quoteARead-onlyInspect
Creates a travel insurance subscription and returns priced offers from HelloSafe partners. Call this once you have collected all required trip details. DATES — follow these rules: (a) if the user gave a concrete start date and either an end date or a duration, use them; (b) if the user gave ONLY a duration (e.g. "20 days") and no start date, default startDate to TOMORROW and compute endDate = tomorrow + duration — do NOT ask them; (c) if the user gave NEITHER concrete dates NOR a duration, OR gave only a vague time frame like "next month", "this summer", "soon", you MUST ask them for the start date and either the end date or duration before calling this tool. COUNTRY OF RESIDENCE — you MUST ask the user where they live before calling this tool unless they have explicitly stated it. NEVER infer countryResidence from the destination, the chat language, or any other indirect signal: residency drives pricing rules, eligibility, and the default currency, so a wrong inference produces incorrect quotes. IMPORTANT: tripInfo.countryResidence and every tripInfo.arrivalCountries entry MUST be ISO 3166-1 alpha-2 country codes (exactly 2 letters), e.g. "FR", "US", "MV" (do NOT pass country names like "Maldives"). tripInfo.tripPrice is PER TRAVELLER (not the total for all travellers) — the system multiplies by the number of travellers internally. If shouldCoverCancellation=true, you MUST ask the user for the actual trip price before calling this tool (cancellation eligibility depends on it). Otherwise NEVER ask: silently default tripPrice to -1 (this is the same sentinel value the in-app comparator sends when the user has not entered an amount; the server then normalizes it for each partner). Coverage opt-ins (shouldCoverCancellation, shouldCoverExtremeSports, studiesInterruption) MUST default to false — only set to true if the user explicitly asks for that specific coverage. Each one restricts the set of offers shown. Each returned offer includes a subscribeUrl — show it as a CTA button so the user can click to complete their purchase.
| Name | Required | Description | Default |
|---|---|---|---|
| locale | Yes | ||
| tripInfo | Yes | ||
| subscriptionId | No | ||
| displayCurrency | No |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description claims the tool 'creates a travel insurance subscription', implying a write operation, but annotations set readOnlyHint=true, indicating it does not modify data. This is a direct contradiction. Additionally, no side effects or permissions are disclosed beyond what annotations provide.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is moderately concise, packed with essential information, and front-loaded with purpose and usage. The only minor improvement would be trimming the details about subscribeUrl, which could be part of the output handling, but overall it is efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema, the description provides some context on the response (offers with subscribeUrl) but does not fully describe the structure of offers or other return fields. For a tool with 4 parameters and nested objects, it covers input constraints adequately but lacks output completeness.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Despite 0% schema description coverage, the description adds value by specifying format requirements (ISO codes for countryResidence and arrivalCountries) and default behavior for shouldCoverCancellation. However, it does not cover all parameters (e.g., locale, subscriptionId, displayCurrency) or nested fields like travellers, leaving gaps.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool creates a travel insurance subscription and returns offers, using specific verbs ('creates', 'returns') and resources ('subscription', 'offers'). It also provides context on when to call it ('once you have collected all required trip details'). No sibling tools exist, so no differentiation needed.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly instructs the AI to call this tool after gathering all trip details and provides critical coding guidelines such as ISO 3166-1 alpha-2 country codes and handling of the shouldCoverCancellation field. It effectively tells the AI when and how to use the tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!