Skip to main content
Glama
MCP Urdu Toolkit

MCP Urdu Toolkit

format_pkr

Format rupee amounts with lakh/crore grouping and optional Urdu word forms, such as "12 lakh 50 hazar," for clear South Asian currency presentation.

Instructions

Format a rupee amount with lakh/crore grouping, e.g. 1250000 -> "Rs 12,50,000" / "12 lakh 50 hazar".

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": {
      "amount": "<amount>"
    },
    "name": "format_pkr"
  }
}

Input Schema

NameRequiredDescriptionDefault
wordsNo
amountYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses the return shape via an example but says nothing about which of the two shown forms is actually returned, how the `words` flag affects output, rounding of decimal amounts, handling of negative or zero values, or the currency assumption behind 'rupee'/'lakh/crore'. That is a substantial gap for a zero-annotation tool.

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?

One front-loaded sentence plus an inline example, with no wasted wording. It loses a point only because the slash-separated dual output is ambiguous as to which value is actually returned, so the compactness costs a bit of precision.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter formatting utility with no output schema, the example output covers the return value reasonably. However, the default/behavior of `words` and edge cases (decimals, negatives, non-PKR inputs) are omitted, so an agent cannot predict results in non-trivial calls.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must explain both parameters. It clarifies `amount` as a rupee value through the example, but `words` (boolean, default true) is never mentioned; the dual output text ("Rs 12,50,000" / "12 lakh 50 hazar") hints at two renderings without ever tying them to the flag, leaving the agent to guess what it controls.

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?

The description gives a specific verb (format), a specific resource (a rupee amount), and a concrete conversion example (1250000 -> "Rs 12,50,000" / "12 lakh 50 hazar"). The sibling tools (convert_digits, hijri_date, normalize_pk_phone, urdu_text_stats) are in entirely different domains, so no explicit contrast is needed for an agent to disambiguate.

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 tool formats a number into Pakistani rupee display form. There is no statement of when to prefer it over format/string handling elsewhere, no mention of the default output form, and no note about the two output styles shown in the example. For a simple utility this is acceptable but not instructive.

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