Skip to main content
Glama

Destination coverage and local networks

get_destination_coverage
Read-only

Shows the countries and published local mobile networks for a Horizon destination, with currently verified 4G/5G claims. Use for regional coverage, a stopover, or manual network selection. Country inclusion does not guarantee signal everywhere, and an absent radio claim does not prove a network lacks that technology. This describes new-sale catalog coverage, not a customer's purchased plan or current location.

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": "<destination>"
    },
    "name": "get_destination_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
destinationYes

Output Schema

NameRequiredDescriptionDefault
urlYes
countriesYes
destinationYes
limitationsYes
catalogUpdatedAtYes
radioClaimsValidUntilYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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=true and destructiveHint=false, so safety is covered; the description goes beyond them with interpretation caveats an agent needs — country inclusion does not guarantee signal everywhere, and an absent radio claim does not prove a network lacks that technology.

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?

Four sentences, front-loaded with what is returned and followed by use cases and two precise caveats; each sentence carries information. Slight density of caveats at the end, but nothing is redundant with the schema or annotations.

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?

An output schema exists, so return values need no explanation, and the description covers scope, use cases, and the main misreading risks. The one remaining gap is the meaning/format of the destination argument.

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?

The single parameter has 0% schema description coverage (only type and 2–80 length bounds), and the description says only "for a Horizon destination." It never states whether the value is a country name, city, destination ID, or code, leaving the agent to guess the accepted format.

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 — shows countries and published local mobile networks with verified 4G/5G claims for a Horizon destination — plus the scope qualifier that this is new-sale catalog coverage rather than a purchased plan, which separates it from list_destination_plans.

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?

"Use for regional coverage, a stopover, or manual network selection" gives concrete use cases, and the closing sentence carves out what the tool is not for (a customer's purchased plan or current location). No sibling tool is named as an explicit alternative, so routing still requires some inference.

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