Skip to main content
Glama
bangladesh-mcp

bangladesh-mcp

by sarif-mia

convert_digits

Read-onlyIdempotent

Converts digits between English (0-9) and Bangla (০-৯) in any text, enabling localized numbers for Bangladesh content.

Instructions

Convert digits between English and Bangla.

Args: text: Any text containing digits. to: "bn" for Bangla digits (০-৯) or "en" for English digits (0-9).

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
toNobn
textYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and repeatability are covered. The description adds that input may be arbitrary text containing digits (i.e., mixed content is handled, not just bare numerals), which is genuine extra context, but it omits edge behavior such as already-converted digits or invalid `to` values. This is useful but thin beyond the annotations.

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-line purpose followed by a compact Args block; front-loaded and free of filler. The Args section is a docstring convention that duplicates schema field names, but given 0% schema coverage that space earns its place.

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

Completeness5/5

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

This is a simple two-parameter pure transformation with a declared output schema, so return values need not be described. Purpose, input domain, and accepted argument values are all present; nothing an agent needs to invoke it correctly is missing.

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%, so the description carries the full burden and largely does: `text` is explained as any text containing digits, and `to` is given concrete accepted values with rendered glyph examples (০-৯ / 0-9). It does not state that `to` defaults to "bn", but the value domain — the part most likely to cause a bad call — is covered.

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 a specific verb and resource ("Convert digits") and the transformation domain (English ↔ Bangla), which is unambiguous against siblings like amount_in_words or calculate_expression. It stops short of explicitly stating what it is not, but the purpose is immediately legible.

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?

"Any text containing digits" implies the input context and the `to` argument implies the direction, so usage is inferable. There is no explicit when-to-use/when-not guidance or note about precedence versus siblings that also touch numbers.

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