Skip to main content
Glama

MeiSIM USA

Get a price quote

get_quote
Read-only

Confirm the current USD price for a specific eSIM plan before purchasing. Returns the full plan plus a price breakdown and a short-lived quote. Call after search_plans, before purchase.

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

Input Schema

NameRequiredDescriptionDefault
plan_idYesThe plan_id (productId) returned by search_plans.

Output Schema

NameRequiredDescriptionDefault
planYes
totalYes
buy_urlNo
how_to_buyNo
quote_expires_atYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds genuinely new behavior by disclosing that the returned quote is short-lived and that the response bundles the full plan with a price breakdown. It stops short of stating currency-conversion or expiry mechanics for the quote, so it is not fully transparent.

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?

Three short sentences, front-loaded with the purpose, then the return content, then the workflow position. No filler or redundancy.

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?

A one-parameter read-only tool with a full output schema needs little more; the description covers purpose, sequencing, and the salient return characteristics. Nothing an agent needs to call it correctly is missing.

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 coverage is 100% and the single plan_id parameter is already documented as coming from search_plans. The description reinforces that a specific plan is being priced but adds no new syntax or format detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('Confirm the current USD price for a specific eSIM plan') plus the return content (full plan, price breakdown, short-lived quote). This clearly separates it from siblings like search_plans (discovery) and purchase (transaction).

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?

Explicitly positions the tool in a workflow: 'Call after search_plans, before purchase,' naming both the prerequisite and the successor. An agent can place this step correctly without inferring anything from sibling names.

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.