Skip to main content
Glama
MCP Urdu Toolkit

MCP Urdu Toolkit

normalize_pk_phone

Normalize Pakistani phone numbers in Latin or Urdu digits to +92 E.164, then identify mobile network or landline city.

Instructions

Normalise a Pakistani phone number (any format, Latin or Urdu digits) to +92 E.164, and say if it is a mobile (with its original network) or a landline (with its city).

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": {
      "phone": "<phone>"
    },
    "name": "normalize_pk_phone"
  }
}

Input Schema

NameRequiredDescriptionDefault
phoneYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose meaningful behaviour: tolerance for Latin or Urdu digits, the canonicalised output form, and the extra mobile/landline classification with network or city. It does not say what happens on an unparseable input (error vs. null), which is the main residual gap.

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?

One sentence pair, front-loaded with the operation and its output format, with no filler. Every clause (format tolerance, E.164 target, mobile/landline distinction) adds information an agent needs.

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 pure transformation with no output schema, the description explains the return semantics itself (E.164 value plus mobile/landline classification), which is the critical missing piece elsewhere. Only error/failure behaviour remains unspecified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single property is bare ('Phone'), so the description must compensate; 'any format, Latin or Urdu digits' adds genuine meaning about accepted input, including Urdu numerals. It stops short of examples or length/prefix expectations, but it is well above the bare schema.

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 and resource ('Normalise a Pakistani phone number') plus the exact output contract ('+92 E.164') and the secondary classification (mobile with original network, landline with city). This scope distinguishes it from neighbouring formatting/digit tools without needing to name them.

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 phrase 'any format, Latin or Urdu digits' implies when the tool applies broadly, but there is no explicit when-to-use/when-not guidance and no routing to alternatives such as format_pkr or convert_digits. Usage is inferable rather than stated.

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