Skip to main content
Glama
Sign In

APIVerve

by com.apiverve
OverviewDiscussionsAdmin

Country Calling Code

CountryCallingCode
Read-only

Country Calling Code: Country Calling Code is a phone number country code API that looks up international dialing codes and official names from a two-letter ISO country code. It returns an array of calling prefixes, standard country identifiers and, on request, the country's exit and trunk prefixes, other regions sharing its code, valid number lengths and example numbers by line type. (Cost: 1 credit)

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": {
      "country": "<country>"
    },
    "name": "CountryCallingCode"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryYesThe 2 letter ISO code for the country (e.g. FR)
dialingNoInclude the dialing block: the international prefix, and (paid plans) the national prefix, regions sharing the calling code, valid number lengths and example numbers

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNoError message, null on success
statusNo"ok" on success

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful context beyond that: a one-credit cost and the fact that richer fields (exit/trunk prefixes, regions, lengths, examples) are only returned on request. It does not cover error behavior for unknown codes or whether responses are cached, so it stays mid-range.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The lead is front-loaded with the core verb and resource, but the opening repeats the tool name twice ('Country Calling Code: Country Calling Code is...') and the long enumeration of return fields is a run-on. It is serviceable but not tight.

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 two-parameter, read-only lookup with a complete schema and an output schema, the description supplies what is missing: what the lookup returns, the optional-detail behavior, and the credit cost. Only the absence of sibling differentiation and error semantics holds it below 5.

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%, so both parameters are already documented, including the two-letter ISO format and the dialing block. The description restates the optional dialing content without adding syntax, format, or edge-case guidance beyond the schema. 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?

Specific verb and resource: 'looks up international dialing codes and official names from a two-letter ISO country code.' An agent can tell this is a phone-dialing-code lookup rather than a generic country-data tool. It does not explicitly distinguish itself from nearby siblings such as CountryLookup or PhoneNumberValidator, which keeps it at 4.

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?

Usage is only implied: give an ISO code, get calling prefixes, with optional dialing details 'on request.' There is no statement of when to prefer this over CountryLookup or PhoneNumberValidator, and no exclusions or prerequisites beyond the paid-plan note.

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

All APIVerve 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