Skip to main content
Glama
MCP Urdu Toolkit

MCP Urdu Toolkit

convert_digits

Converts digits in text between Urdu numerals and Latin 0-9, letting you switch scripts for localized or standard number display.

Instructions

Convert the digits in text to Urdu digits (to="urdu") or back to 0-9 (to="latin").

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": {
      "text": "<text>"
    },
    "name": "convert_digits"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNourdu
textYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description bears the full burden, and it does not state that this is a non-destructive, reversible text transformation or what happens to non-digit characters and mixed content. The existence of an output schema removes the need to describe return values, which keeps this from being a larger 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?

A single sentence, front-loaded with the verb and resource, with the mode values attached directly to their meanings. Nothing is redundant and nothing is buried.

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 text transformation with an output schema and no annotations, the description covers purpose and both mode values adequately. It stops short of describing handling of non-digit characters or mixed Latin/Urdu digit input, which is the only real completeness gap.

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 coverage is 0% and the 'to' property has no enum in the schema, so the description's enumeration of "urdu" and "latin" adds genuine meaning that the agent could not otherwise obtain. The 'text' parameter is not described beyond 'the digits in text', which is nearly self-evident but leaves edge cases unaddressed.

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 pairs a specific verb ('Convert') with a specific resource ('the digits in text') and names both directions of conversion. It is narrow enough that an agent can distinguish it from normalize_pk_phone or urdu_text_stats without inspecting the schema, though it never names a sibling explicitly.

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 two modes are spelled out inline with their parameter values, so the agent knows which direction to request (to="urdu" vs to="latin"). There is no when-not guidance, no mention of alternatives such as full text translation, and no note about mixed-script input.

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