Skip to main content
Glama

NS Pros MCP Gateway

numverify__numverify_countries

List the countries supported by Numverify, with their ISO country code, name, and international dialing prefix. Example: numverify_countries({ _apiKey: "your-key" })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "_apiKey": "your-numverify-api-key"
    },
    "name": "numverify__numverify_countries"
  }
}

Input Schema

NameRequiredDescriptionDefault
_apiKeyYesNumverify/APILayer API key. Free signup at https://numverify.com/product; key is on your APILayer dashboard.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. 'List' implies a safe read-only operation, and it discloses the shape of each returned row (ISO code, name, dialing prefix), which is useful. However, it says nothing about whether the list is static or live, ordering, result size, rate limits, or that an API key is mandatory for access.

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?

Two short sentences, front-loaded with the resource and returned fields, followed by a compact invocation example. Nothing is redundant or padded.

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 single-parameter, no-output-schema reference tool, the definition covers what an agent needs: what the list contains and the key required to call it. The only soft spots are the absence of a when-to-use hook and any note on result size or ordering, which are minor for a finite country list.

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?

There is only one parameter (_apiKey) and schema coverage is 100%, with the schema itself explaining the key source and signup URL, so the baseline of 3 applies. The example call reiterates the required key but adds no new meaning about the parameter beyond the schema.

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?

The description uses a specific verb and resource ('List the countries supported by Numverify') and names the exact fields returned (ISO code, name, dialing prefix), so an agent can immediately tell this is a static reference-lookup tool rather than a validation tool like numverify_validate. It stops short of explicitly contrasting itself with siblings, but the purpose is unambiguous.

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: the agent can infer this is the place to get country codes or dialing prefixes before calling a validation tool, but the description never states when to use it, when not to, or that it is the reference source for numverify_validate inputs. No alternatives or prerequisites are mentioned.

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.