Skip to main content
Glama
bangladesh-mcp

bangladesh-mcp

by sarif-mia

amount_in_words

Read-onlyIdempotent

Converts BDT amounts into English or Bangla words using lakh/crore for invoices and cheques, with optional 'Only' suffix.

Instructions

Write a taka amount in words for invoices and cheques, using lakh/crore.

Args: amount: Amount in BDT; up to two decimals are read as paisa. language: "en" for English or "bn" for Bangla. include_only: Add "Only" / "মাত্র" at the end.

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

Input Schema

NameRequiredDescriptionDefault
amountYes
languageNoen
include_onlyNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/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 is covered; the description adds genuinely new behavior: lakh/crore grouping, that up to two decimals are interpreted as paisa, and that include_only appends "Only" / "মাত্র". It does not mention rounding for inputs with more than two decimals or handling of negative/zero amounts, which are the remaining behavioral gaps for a conversion function.

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 states purpose and convention, followed by a compact Args block for the three parameters. It is well sized and every line earns its place; the slight redundancy between the prose and the args list is negligible.

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 pure read-only conversion with a required amount, the definition covers purpose, numbering system, currency unit, language options and the optional suffix. An output schema exists, so return format need not be restated. Only edge-case behavior (rounding of extra decimals, negatives) is left unspecified.

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 it documents all three parameters: amount is in BDT with two decimals read as paisa, language takes the values "en" or "bn" (the schema only says string with default en and has no enum), and include_only appends a suffix. This meaningfully exceeds the bare schema, though it omits formatting details such as the word for zero or sub-paisa rounding.

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?

"Write a taka amount in words for invoices and cheques, using lakh/crore" gives a specific verb (write/convert) plus the exact resource (a BDT amount rendered as words) and the numbering convention, which distinguishes it from numeric siblings like convert_digits or calculate_expression. It stops short of naming an alternative tool, but the domain is unambiguous.

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?

The phrase "for invoices and cheques" implies the intended context (formal documents needing amounts spelled out), but there is no explicit when-to-use vs when-not guidance and no reference to any sibling tool. An agent can infer the use case, yet nothing steers it away from misuse such as passing non-monetary numbers.

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