get_destination_infoCoverage (ISO country codes), mobile operators, top-up availability and entry price for a destination.
| Name | Required | Description | Default |
|---|---|---|---|
| locale | No | en | |
| destination | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
There are no annotations, so the description carries the full burden of behavioral disclosure. It indicates the returned information types but does not explicitly state side effects, whether the operation is read-only, or whether calling it incurs internal effects. The 'get' in the name suggests read-only, but the description itself does not make this explicit.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single compact sentence with no filler or repetition of the tool name. It front-loads the most important content, compatibility, and lists the remaining returned data efficiently. Every phrase adds value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with two parameters, no output schema, and no annotations, the description is too sparse. It names the output content categories but omits essential detail such as what values destination can accept, how locale affects the data, and what constitutes an exact output or empty result. It also lacks any routing or caveat information.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the description does not explain the meaning or expected format of the destination parameter, nor does it clarify how locale affects the response. It mentions the concept of destination and the data returned for it, but leaves both parameters underspecified.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies what the tool provides: coverage (ISO country codes), mobile operators, top-up availability, and entry price for a given destination. It is concrete and tied to a specific resource, though it does not strongly distinguish itself from sibling tool 'check_coverage'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is given about when to use this tool versus the siblings. For example, it does not explain how get_destination_info differs from check_coverage or list_destinations, nor when one would prefer one over the other. The usage context must be inferred by the agent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clear primary purpose, but check_coverage and get_destination_info both provide coverage-related information, and recommend_plan/search_plans can overlap in plan selection. Descriptions are detailed enough to guide an agent, though a few boundary cases remain.
All tool names follow a consistent verb_noun pattern: check_, create_, get_, list_, recommend_, search_. The verbs are distinct and the nouns clearly identify the resource being acted on.
Seven tools is well-scoped for an eSIM connectivity server, covering coverage, destination info, plan discovery, recommendation, and checkout without unnecessary duplication.
The tool set covers coverage checks, destination details, plan search/retrieval, recommendations, and checkout handoff. Minor gaps exist around top-up actions and post-purchase order management, but the core connectivity workflow is well covered.