Skip to main content
Glama
MCP Urdu Toolkit

MCP Urdu Toolkit

urdu_text_stats

Count words and characters in Urdu or Roman/Latin text, detect the script, and estimate reading time.

Instructions

Count words and characters, detect Urdu vs Roman/Latin script, and estimate reading time.

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": "urdu_text_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
words_per_minuteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and falls short. It doesn't say what the response contains (no output schema exists), how script detection behaves on mixed Urdu/Latin text, or whether reading time assumes the wpm parameter. The only behavioral hints are the three operations themselves.

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 well-formed sentence listing the three capabilities with no filler. It is front-loaded and every clause earns its place.

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

Completeness2/5

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

For a tool with no annotations, no output schema, and 0% parameter documentation, the description should explain the return shape and parameter effects. Instead it leaves the agent unable to predict the result format or how `words_per_minute` changes the output.

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% for two parameters. The description never mentions the required `text` input or the `words_per_minute` parameter, so the connection between that parameter and 'estimate reading time' must be guessed. It adds essentially no meaning beyond the schema property names.

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 names three specific operations: counting words/characters, detecting Urdu vs Roman/Latin script, and estimating reading time. That is a concrete verb+resource statement an agent can match to a request. It does not explicitly differentiate from siblings, though the sibling names (convert_digits, format_pkr, hijri_date, normalize_pk_phone) are in unrelated domains, so confusion risk is low.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no statement of when this tool is the wrong choice. The capability list implies usage but leaves the agent to infer whether, for example, script detection is needed before calling a normalization tool.

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