Skip to main content
Glama
bangla-calendar
by FAsami

bangla_to_gregorian

Read-only

Convert a Bangladesh Bengali calendar date using month numbers, English names, or Bengali script into a Gregorian YYYY-MM-DD date for scheduling and record matching.

Instructions

Convert a Bangladesh Bengali calendar date to a Gregorian date (YYYY-MM-DD). Month can be 1-12 (Boishakh = 1), an English spelling such as 'Poush', or Bengali script.

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": {
      "day": "<day>",
      "month": "<month>",
      "year": "<year>"
    },
    "name": "bangla_to_gregorian"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayYesDay of the Bengali month, 1-31
yearYesBengali year (Bangabda), e.g. 1433
monthYesBengali month: 1-12 or its name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description carries the rest: it discloses the exact return format (YYYY-MM-DD) and the three accepted month input forms. It does not mention behavior for out-of-range days or years, but for a pure read-only conversion the added context is substantial.

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?

Two sentences, zero filler, with the operation and output format front-loaded before the input-format detail. Every clause adds information an agent needs.

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?

No output schema exists, and the description compensates by naming the return format. Minor gaps remain around accepted year ranges (the schema permits arbitrarily large and negative integers) and error behavior for invalid day/month combinations, which matters for a date-conversion tool.

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 coverage is 100%, so the baseline is 3, but the description genuinely adds meaning beyond the schema's '1-12 or its name': it pins the numbering anchor (Boishakh = 1), gives a concrete spelling example ('Poush'), and confirms Bengali script is accepted. This directly resolves the ambiguity of an anyOf integer/string parameter with no enum.

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?

States a specific verb and resource plus the direction of conversion and the output format: 'Convert a Bangladesh Bengali calendar date to a Gregorian date (YYYY-MM-DD).' The one-way direction makes it trivially distinguishable from the sibling gregorian_to_bangla without opening either schema.

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

Usage Guidelines4/5

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

The conversion direction establishes clear context for when this tool applies versus the reverse-direction sibling, but there is no explicit exclusion clause or note about invalid/impossible dates. Adequate routing information, no stated when-not.

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