A
license-
qualityC
maintenanceRead-only MCP server and JSON API for international country calling codes, ISO country codes, E.164 dial codes, regions, trunk prefixes, and NANP area codes.
MIT
Country Calling Codes
Server Details
Country calling codes, ISO codes, E.164 dial codes, regions, trunk prefixes, and NANP area codes.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4.4/5.0
Tool DescriptionsA
Average 4.4/5 across 2 of 2 tools scored.
Server CoherenceA
Disambiguation5/5
Each tool has a clearly distinct purpose: one formats phone numbers into international format, the other looks up country calling codes. No overlap in functionality.
Naming Consistency5/5
Both tool names follow a consistent verb_noun pattern with underscores (format_international_phone_number, lookup_country_calling_code), making them predictable and readable.
Tool Count4/5
With only two tools, the server is minimal but appropriate for its narrow domain. While slightly under the typical range, each tool serves a distinct and necessary function.
Completeness4/5
The tool set covers the core workflow of looking up a country code and formatting a number. Minor gaps like validation or listing all codes exist, but they are not essential to the stated purpose.
Available Tools
2 toolsformat_international_phone_numberFormat International Phone NumberARead-onlyIdempotentInspect
Normalize a phone number into a plausible international format using reviewed country-specific rules. Processing is ephemeral. This tool does not query carriers, HLR/HSS, MNP databases, or live subscribers.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| countryCode | No | Optional ISO 3166-1 alpha-2 country context, such as GB. | |
| phoneNumber | Yes | Phone number to format. It is processed ephemerally and is not stored. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| meta | Yes | |
| result | Yes | |
| limitations | Yes |
Tool Definition Quality
A4.5/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the annotations, the description adds that processing is 'ephemeral' and that the tool does not query live carrier databases. This is valuable contextual information about the tool's offline, non-validating nature, going beyond what readOnlyHint and idempotentHint already convey.
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?
The description is two concise sentences, with the primary purpose front-loaded in the first sentence and supplementary behavioral details in the second. There is no redundant wording or unnecessary information, making it efficiently structured.
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?
The description is complete for this simple tool: it covers purpose, privacy (ephemeral processing), and scope (carrier-query exclusion). Given the full schema, annotations, and output schema, no critical information is missing for an agent to decide whether and how to invoke the tool.
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 input schema provides 100% coverage for both parameters with clear descriptions. The tool description does not significantly expand on the parameters, merely implying that countryCode supplies country context. Since the schema already does the heavy lifting, the description adds little parameter-specific value.
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 uses a specific verb ('Normalize') and clearly identifies the resource ('a phone number') and the outcome ('international format'). It also mentions 'reviewed country-specific rules,' which distinguishes it from the sibling tool that merely looks up country calling codes, avoiding confusion with validation or live lookup.
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?
The description explicitly states what the tool does not do ('does not query carriers, HLR/HSS, MNP databases, or live subscribers'), providing a clear boundary for when not to use it. However, it does not explicitly name the sibling tool as an alternative, so the guidance is clear but not fully explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
lookup_country_calling_codeLookup Country Calling CodeARead-onlyIdempotentInspect
Look up international country calling codes by free text, ISO code, dial code, or region. Optionally return reviewed, source-linked dialing examples. This tool does not verify live subscriber numbers.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| q | No | Free-text search, such as "United Kingdom", "London", or "AUS". | |
| code | No | ISO 3166-1 alpha-2 or alpha-3 code, such as GB or GBR. | |
| limit | No | Maximum number of countries to return. | |
| region | No | Optional region filter. | |
| dialCode | No | Calling code with or without plus sign, such as +44 or 44. | |
| includeExamples | No | When true, include reviewed safe mobile/landline patterns, transformation rules, source URLs, and lastVerified metadata. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| meta | Yes | |
| query | Yes | |
| countries | Yes |
Tool Definition Quality
A4.3/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds useful context beyond the readOnly and idempotent annotations: examples are 'reviewed, source-linked', and it explicitly warns that live numbers are not verified. This is genuine behavioral disclosure, though it doesn't go into details like rate limits or response structure.
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?
The description is two sentences long and front-loaded with the core action. The optional examples feature is briefly mentioned, followed by the limitation. Every sentence earns its place with no redundancy or filler.
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?
The tool is a simple lookup with a full output schema and 100% schema coverage for parameters. The description adds the key limitation (no live number verification) and the nature of the examples. Given its simplicity and rich structured metadata, the description is complete enough for correct selection and invocation.
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 input schema provides 100% parameter coverage with detailed descriptions for all six parameters. The description maps high-level search methods (free text, ISO code, dial code, region) to corresponding parameters but doesn't add deeper syntax or format details beyond what the schema already states.
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 specifies exactly what the tool does: 'Look up international country calling codes' with supported search methods (free text, ISO code, dial code, region). This clearly distinguishes it from the sibling tool 'format_international_phone_number', which formats rather than looks up.
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?
The description gives clear context: use this tool to look up country calling codes. It also notes an important exclusion: 'This tool does not verify live subscriber numbers.' However, it does not explicitly name the sibling tool as an alternative when formatting is needed, so it misses the 'alternatives' criterion for a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- Alicense-qualityCmaintenanceValidates phone numbers and provides country calling codes, enabling AI agents to look up international dialing codes and filter by country name, ISO code, or calling code.11MIT
- AlicenseAqualityBmaintenanceProvides North American (NANP) area code and phone number intelligence for AI agents, including area code lookup, phone validation, carrier info, city/state coverage, local time, and scam context.852MIT
- Alicense-qualityCmaintenanceProvides world country data from the REST Countries API, enabling search by name, ISO code, region, language, or currency, with details like capital, population, and languages.10MIT