Skip to main content
Glama

esimdata: travel eSIM comparison

Compare eSIM plans

compare_plans
Read-onlyIdempotent

Put 2 to 10 plans (ids from search_plans) side by side with the same fields, in the order given, to help a traveller choose.

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

Input Schema

NameRequiredDescriptionDefault
plan_idsYesIds exactly as search_plans returned them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / plan_ids / description
      Added value: +"Ids exactly as search_plans returned them."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds behavior annotations don't: output is aligned with identical fields across plans, and input order is preserved in the result. With no output schema, that return-shape information is genuinely load-bearing. Error behavior for invalid or unknown ids is not mentioned.

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?

One sentence, front-loaded with the action and the constraints, no filler. Every clause carries information: count bounds, id provenance, output alignment, ordering, and intended user decision.

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 one-parameter, non-destructive read tool with rich annotations, the description covers the essentials, including the result shape it must supply in the absence of an output schema. What remains uncovered is failure handling for stale or malformed ids, a minor gap given the tool's simplicity.

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 100% and the single property is well documented ('Ids exactly as search_plans returned them'), so the baseline is 3. The description adds meaning beyond the schema by tying the array to search_plans output and establishing that the order of the ids controls the order of the comparison, which the schema does not state.

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?

States a specific verb-and-resource ('Put ... plans ... side by side') plus concrete scope: 2 to 10 plans, ids sourced from search_plans, order preserved, same fields. An agent can immediately tell this is a comparison tool rather than a lookup. It stops short of naming the sibling to use for a single plan (get_plan), so sibling differentiation is implied by the 2-10 range rather than stated.

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

Usage Guidelines4/5

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

Gives clear context: this follows search_plans (ids must come from there) and serves a specific decision ('help a traveller choose'). The workflow ordering is explicit. No exclusions are stated, e.g. that a single plan should go through get_plan, but the minimum of 2 plans implicitly excludes that case.

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