Skip to main content
Glama
bangla-calendar
by FAsami

to_bangla_digits

Read-only

Convert digits 0-9 in numbers or text to Bengali numerals (০-৯) for Bengali calendar displays, forms, and localization.

Instructions

Write a number or text with Bengali digits (০-৯) instead of 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": "to_bangla_digits"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText or number to convert

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes that no mutation occurs. The description adds useful transformation semantics by indicating digit substitution, but it does not explain how mixed text, non-digit characters, or already-Bengali digits are handled.

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?

The description is a single front-loaded sentence with no unnecessary elaboration. The wording 'Write a number or text' is slightly awkward but does not impede understanding.

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 simple one-parameter read-only conversion tool, the description is minimally sufficient to invoke it. However, with no output schema it could be clearer about what the returned string looks like and how non-digit content is preserved.

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

Parameters3/5

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

Schema coverage is 100%, and the schema already defines the single 'text' parameter. The description adds only a minor clarification that the input may be a number or text, without new format or edge-case detail.

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 states a specific transformation: writing numbers or text using Bengali digits (০-৯) instead of ASCII 0-9. This clearly identifies the tool's operation and direction, though it does not explicitly differentiate it from sibling conversion tools.

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?

The description gives no explicit when-to-use guidance, exclusions, or alternatives. Usage is only implied by the conversion purpose itself.

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