travel-insurance

check_card_coverage

Read-only

Use HelloSafe to check what travel insurance a credit card already includes, from the card's real terms & conditions. Call whenever the user asks what their card covers for a trip (medical, cancellation, baggage, ski…), whether their card is enough, or mentions relying on their card's insurance. Identify the card from its name (and bank / country when given). Returns the real covered guarantees with amounts and conditions, plus the coverage gaps for the trip. If gaps exist, offer to get complementary travel-insurance quotes via get_quote, passing this card's id as cardId so the offers are ranked by how well they fill the gaps. Never invent coverage: only state what this tool returns.

Input Schema

TableJSON Schema

Name	Required	Description
`cardId`	No	Exact HelloSafe card ID from a previous call — use it to re-check a specific candidate instead of fuzzy matching.
`locale`	No	Language the user is conversing in, as a BCP 47 tag or 2-letter code (e.g. "fr", "pt-BR"). ALWAYS pass it.
`network`	No	Card network when stated: "Visa", "Mastercard", "Amex".
`cardQuery`	No	Card name as the user said it, expanded ("American Express Platinum", not "Amex Plat"). Include the bank when known ("Chase Sapphire Reserve"). Omit only when cardId is provided.
`bankCountry`	No	ISO-2 country of the issuing bank (e.g. "US", "FR"). Defaults to the user's country of residence when known — greatly improves matching.
`tripContext`	No	Optional trip details — sharpen the gap analysis. Omit what you do not know.

Output Schema

TableJSON Schema

Name	Required	Description
`card`	No	The card the analysis is about.
`gaps`	No	Guarantees missing or insufficient for the trip — the offer features a complementary policy should provide.
`error`	No	Human-readable reason when the check could not run. Absent on success.
`covered`	No	Travel guarantees the card really includes, with amounts and conditions from the card T&Cs.
`unknown`	No	Core guarantees with no data on this card — phrase as "not documented, check your contract", never as "not covered".
`alternatives`	No	Other cards matching the query. If the analysed card is not the user's, ask which one and call again with its cardId.
`allGuarantees`	No	The card's FULL guarantee sheet, grouped by section (travel first) — render as one markdown table per section: Guarantee \| Your card \| Recommended \| Verdict.
`_assistantGuidance`	No
`cancellationOnlyGap`	No	True when cancellation is the ONLY gap — suggest a cancellation-only policy (intent "cancellation" in get_quote), usually much cheaper.

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 4, 2026

TDQS

A4.6/5.0

Behavior4/5

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

The description adds value beyond annotations by guaranteeing 'Never invent coverage: only state what this tool returns' and noting the data comes from real terms & conditions. This reassures the agent about data fidelity without contradicting the readOnlyHint annotation.

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?

The description is front-loaded with purpose and when-to-use, then logically flows into output and follow-up. It is somewhat verbose but every sentence contributes actionable guidance, and the structure is clear.

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

Completeness5/5

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

With an output schema present, the description focuses on usage context and behavior. It explains the return value (real covered guarantees with amounts and conditions, plus gaps) and the follow-up routing to get_quote. For a tool with 6 parameters and nested objects, this is complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already documents all six parameters with detailed descriptions (100% coverage). The description adds context on when to use cardId vs cardQuery and explains that tripContext sharpens gap analysis, which goes slightly beyond the schema but is not extensive.

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?

The description states a clear verb and resource: 'check what travel insurance a credit card already includes' from real terms & conditions. It distinguishes itself from the sibling get_quote by specifying that get_quote is for complementary quotes after gaps are identified.

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

Usage Guidelines5/5

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

It explicitly lists when to call ('Call whenever the user asks what their card covers for a trip...') with concrete examples. It also provides a clear follow-up action: if gaps exist, offer get_quote and pass the card's id as cardId, which directs the agent to the correct next step.

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

All travel-insurance tools Inspect

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

Need Help?