Skip to main content
Glama

Quote and buy link

get_quote
Read-onlyIdempotent

The price of one plan in the requested currency, and the link where the traveler buys it on getwigoo.com. This tool does not place an order: the purchase happens on the site.

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": {
      "destination_id": "<destination_id>",
      "plan_id": "<plan_id>"
    },
    "name": "get_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
plan_idYesPlan id from list_plans.
currencyNoISO 4217 code for prices, e.g. EUR, GBP, JPY. Defaults to USD.
languageNoLanguage of the buy link and of region names: en, it, es, fr, de, pl, pt, tr. Defaults to en.
quantityNoHow many eSIMs to buy, each for one phone. From 1 to 10, 1 if omitted.
destination_idYesDestination id from search_destinations, e.g. "jp" or "eu-42".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so the safety profile is covered. The description adds one genuinely useful behavioral fact — that no order is placed and the transaction leaves the API for the site — but says nothing about rate limits, caching of quotes, or price validity windows.

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?

Two short sentences, front-loaded with what is returned and followed by the ordering caveat. Nothing is redundant or padded.

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?

With no output schema, the description correctly carries the return-value burden by naming both the price and the buy link. The only gap is not stating whether the price is per-unit or scaled by the quantity parameter.

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

Parameters3/5

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

Schema description coverage is 100%, so field meaning (currency format, language list, quantity 1-10, id sources) is already handled by the schema. The description adds only the phrase 'requested currency' and does not clarify whether the returned price reflects the quantity multiplier, which is the one ambiguity worth resolving.

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?

The description names a specific resource and output: the price of one plan in the requested currency plus the buy link on getwigoo.com. It is easy to distinguish from get_destination, list_plans and search_destinations by its pricing/link output, though it does not name those siblings explicitly.

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?

It sets a clear usage boundary with 'This tool does not place an order: the purchase happens on the site,' which tells an agent this is a read-only quoting step rather than a checkout. No sibling alternatives are named, but the schema already routes the caller to list_plans and search_destinations for the required ids.

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.