Skip to main content
Glama

Widely

by com.widely-mobile
OverviewDiscussionsAdmin

Find a mobile service

discover_services
Read-onlyIdempotent

Find a home mobile service Widely can provide for a country, including eSIM or physical SIM, native voice, SMS, a mobile number, and a regular or kosher line when the offer includes it. No sign-in. An empty list means nothing is listed yet. Travel data for a trip is a separate Widely product.

Input Schema

NameRequiredDescriptionDefault
countryNoCountry name or two-letter code.
capabilityNoOne capability the offer declares, such as native_voice, sms, mobile_number, or number_porting.
form_factorNoesim or physical_sim.
number_lineNoregular or kosher. Returned only when the offer lists that line.
capabilitiesNoEvery capability the offer declares. A missing one is left out.
service_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / capabilities
      Added value: +{
+  "description": "Every capability the offer declares. A missing one is left out.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / capability / description
      Added value: +"One capability the offer declares, such as native_voice, sms, mobile_number, or number_porting."
    • addedInput schema / properties / country / description
      Added value: +"Country name or two-letter code."
    • addedInput schema / properties / number_line
      Added value: +{
+  "description": "regular or kosher. Returned only when the offer lists that line.",
+  "type": "string"
+}
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

Adds context beyond the annotations: 'No sign-in' (no auth required) and 'An empty list means nothing is listed yet' (empty-result semantics) are genuinely useful disclosures. Annotations already cover read-only/idempotent/openWorld, so these extras push it above baseline.

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?

Three compact sentences, front-loaded with the core purpose, then the useful 'empty list' and 'separate product' notes. Minimal waste.

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 and only read-only annotations, the description adequately covers auth ('no sign-in'), empty results, scope, and product boundaries. Slightly missing on what the returned offer objects contain or how capabilities filter vs. filter-by-capability interact.

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 83%, so the schema already documents country, capability, form_factor, number_line, and capabilities. The description largely restates the same values (eSIM, physical SIM, voice, SMS, kosher line) without adding syntax or default behavior. Baseline 3 applies.

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?

States a specific verb+resource ('Find a home mobile service Widely can provide for a country') and clarifies the scope includes eSIM/physical SIM, voice, SMS, etc. It distinguishes itself from the travel-data product but does not explicitly differentiate from closer siblings like quote_service or list_plans.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implied usage (discover what services exist for a country) with one exclusion ('Travel data for a trip is a separate Widely product'), but no explicit statement of when to prefer this over quote_service, quote_esim, or list_plans.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Widely toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources