SimplyGlobal Visitor Insurance

Compare plan benefits side by side

get_visitor_insurance_plan_details

Read-onlyIdempotent

Compare visitor insurance plan benefits side by side for up to 4 plan_ids returned by search_visitor_insurance_plans. Returns the compare page's benefit rows and highlights per plan, plus the brochure link when available. Default sections can be narrowed with the sections input. Pass the same deductible_usd you used in search_visitor_insurance_plans so the benefits and link match that option; without it, details describe the plan's default option ($250 deductible when offered, else the lowest).

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": {
      "trip": "<trip>",
      "plan_ids": "<plan_ids>"
    },
    "name": "get_visitor_insurance_plan_details"
  }
}

Input Schema

Name	Required	Description
`trip`	Yes
`plan_ids`	Yes	One to four plan_id values from search_visitor_insurance_plans.
`sections`	No	Benefit sections to include. Default: all five sections.
`deductible_usd`	No	Optional exact deductible in USD (for example 250 for $250); picks the option the benefits and link describe.

Output Schema

Name	Required	Description	Default
`trip`	Yes
`notes`	Yes
`plans`	Yes
`currency`	Yes
`quote_issued_at`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds non-obvious behavioral detail: the default deductible fallback ($250 when offered, else lowest) and that omitting deductible_usd changes which option the benefits and brochure link describe. It does not discuss pagination or rate limits, but this is a read-only comparison tool.

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?

Three sentences, front-loaded with the purpose, followed by return contents and parameter guidance. It is dense but each clause carries information; the deductible sentence is long but necessary. No filler or repetition.

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 4-parameter tool with a nested trip object and an output schema (so return values need not be explained), the description covers purpose, prerequisites, the key deductible coupling, and section narrowing. The main minor gap is that it doesn't restate trip-object constraints, which the schema handles.

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?

Schema coverage is 75%, so the schema documents most parameters, but the description adds meaningful semantics beyond it: the interaction between deductible_usd and the returned benefits/link, the default fallback deductible, and that sections narrow the default set of all five sections. It does not elaborate on the nested trip fields, which the schema already covers well.

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?

Specific verb and resource: 'Compare visitor insurance plan benefits side by side for up to 4 plan_ids'. It explicitly names the sibling tool that produces the inputs (search_visitor_insurance_plans) and states what is returned (benefit rows, highlights, brochure link), which distinguishes it from the search and link tools.

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 states the prerequisite (plan_ids must come from search_visitor_insurance_plans), the constraint (up to 4), and the condition for narrowing results (sections input). It also gives explicit guidance on passing deductible_usd to match the search option and what happens if omitted.

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

All SimplyGlobal Visitor 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?