Compare travel insurance quotes from 15+ insurers — Schengen, WHV, students, long stays, seniors.
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.
Average 4.6/5 across 1 of 1 tools scored.
Only one tool exists, so there is no possibility of confusion. The tool clearly handles all quote requests.
The single tool name 'get_quote' follows a clear verb_noun pattern, consistent with good naming conventions.
With only one tool for a broadly-named domain like travel insurance, the server feels under-scoped. While the tool is purpose-built for quotes, the count is too low to cover the apparent domain.
The server only offers 'get_quote', missing essential operations like purchasing, canceling, or managing policies. This is a severely incomplete surface for a travel insurance server.
get_quoteAUse this whenever the user wants travel-insurance quotes. Returns priced offers from HelloSafe partners and renders the comparison widget. Required: countryResidence, arrivalCountries, traveller age(s). Everything else has a sensible default — never ask the user for an optional field. After calling, reply with 1-2 short sentences highlighting the recommended offer — never re-list offers as a table, never paste subscribe URLs.
| Name | Required | Description | Default |
|---|---|---|---|
| locale | No | Language of the user. Defaults to the host locale. | |
| tripInfo | Yes | Trip details. | |
| subscriptionId | No | Existing subscription ID to update instead of creating a new one. | |
| displayCurrency | No | ISO 4217 code to override the widget display currency. Omit unless the user explicitly asked for a different display currency than the trip-cost currency. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds behavioral context beyond annotations, such as rendering the comparison widget and instructing the agent to reply with 1-2 sentences highlighting the recommended offer. This provides helpful extra transparency about side effects and response expectations.
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 three sentences, front-loaded with purpose and usage, then post-call instructions. Every sentence earns its place; no redundant content.
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?
The tool has a complex nested schema, no output schema, and full parameter descriptions in the schema. The description explains the output at a high level ('priced offers' and 'comparison widget') and provides necessary agent behavior for call success. It does not detail the return structure, but given the schema's thoroughness, this is a minor gap.
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?
Schema description coverage is 100%, so the baseline is 3. The description adds meaningful guidance: it identifies the truly required fields (countryResidence, arrivalCountries, traveller ages) and establishes a policy that optional fields have sensible defaults and should never be asked for. This goes beyond the schema's individual field descriptions.
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 states 'Use this whenever the user wants travel-insurance quotes' and specifies what it does: 'Returns priced offers from HelloSafe partners and renders the comparison widget.' This is a specific verb+resource purpose, distinguishing the tool even without sibling context.
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?
Provides explicit when-to-use ('whenever the user wants travel-insurance quotes'), required fields, and clear exclusions: 'never ask the user for an optional field' and 'never re-list offers as a table, never paste subscribe URLs.' No alternatives exist, but the 'when not to' is implicitly handled by 'required' and optional policy.
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.
No comments yet. Be the first to start the discussion!
