Skip to main content
Glama

GlobalPass answers: install, start, pay, refund

get_faq
Read-only

Use this to answer questions about buying and using a GlobalPass eSIM in the shop's own words: when the QR code arrives, how to install it, when a plan starts, calls and texts, data running out, payment methods and refunds. Quote these answers rather than general knowledge about eSIMs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_faq"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicNobefore = before buying, install = installing, trip = on the trip, pay = payment and refunds. Omit for all.
languageNoLanguage of the answers: en, pl or ru.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description's valuable addition is the sourcing constraint — answers are the shop's own words and should be quoted, not paraphrased from general eSIM knowledge — but it says nothing about what comes back (single answer vs. multiple snippets, whether an empty result is possible when no topic matches), which matters because there is no output schema.

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 actionable instruction is front-loaded in the opening clause, and the closing sentence adds a genuinely useful behavioral rule rather than filler. The middle topic enumeration is long but each item maps to real coverage, so little is wasted; only the density of the single run-on sentence costs it a point.

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 zero-required-parameter, read-only FAQ lookup with no output schema, the description supplies purpose, topical coverage and a quoting rule — enough to call it correctly. The remaining gap is return-shape ambiguity (one answer or several, and behavior when nothing matches), which is modest given the tool's simplicity.

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 both enum parameters carry their own descriptions, so the baseline is 3. The description's topic list (QR code timing, calls and texts, data running out) loosely fleshes out what 'trip' and 'pay' cover beyond the terse enum text, but it never references the parameters by name and says nothing about the language selector.

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 names a specific verb and resource — answering customer questions about buying and using a GlobalPass eSIM — and enumerates the subject matter (QR code arrival, installation, plan start, calls/texts, data exhaustion, payment, refunds). That scope makes it unmistakable against siblings like check_device, plan_trip and search_plans, which handle device checks, trip planning and plan search rather than shop-authored answers.

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 clearly states the context of use ('answer questions about buying and using a GlobalPass eSIM') and adds a strong directive: quote these answers rather than general eSIM knowledge. It does not name a sibling or say when to prefer one — e.g. a device-compatibility question routed to check_device — so the routing guidance is implicit rather than explicit.

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