Skip to main content
Glama

NS Pros MCP Gateway

numverify__numverify_validate

Validate a phone number and look up its carrier, line type (mobile/landline), country, and location. Returns international/local formats too. Accepts E.164 (e.g. "+14158586273") or a local number with country_code. Example: numverify_validate({ number: "14158586273", _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": {
      "number": "+14158586273",
      "_apiKey": "your-numverify-api-key"
    },
    "name": "numverify__numverify_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
numberYesPhone number to validate. E.164 like "+14158586273" or "14158586273", or a local number when country_code is supplied, e.g. "4158586273".
_apiKeyYesNumverify/APILayer API key. Free signup at https://numverify.com/product; key is on your APILayer dashboard.
country_codeNoOptional ISO 3166-1 alpha-2 country code (e.g. "US", "GB"), required only when `number` is in local/national format rather than international.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose the return payload (carrier, line type, country, location, formats), which is genuinely useful. However it never states that this is a read-only lookup, never mentions numverify's request quota (a real constraint on a free API key), and doesn't say whether an invalid number yields an error or a validity=false response.

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?

Front-loaded with the capability and return fields, then input formats, which is the right order. The trailing example call largely repeats what the schema examples already show, so one sentence is close to dead weight.

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 simple three-parameter read tool with no output schema, the description covers capability, accepted input formats, and the shape of the response, which is enough for an agent to call it correctly. The main gap is operational context (quota, invalid-number behavior) rather than anything structural.

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 100%, so the baseline is 3. The description adds only marginal meaning beyond the schema: it restates the E.164/local-plus-country_code relationship and includes an example call that duplicates the schema's own examples rather than adding constraints or edge cases.

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 (validate) plus the resource (phone number) and enumerates exactly what enrichment is returned: carrier, line type, country, location, and international/local formats. The phone-number resource distinguishes it from every listed sibling, which are all generic *_validate_claim tools for unrelated datasets.

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?

The description gives clear input-format routing (E.164 directly, or local number plus country_code), which is the main usage decision an agent faces here. It gives no when-to-use versus when-not-to-use guidance, no mention of rate limits or free-tier caps, and no statement about what happens with an invalid/unparseable number.

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.