Skip to main content
Glama
bangla-calendar
by FAsami

gregorian_to_bangla

Read-only

Converts a Gregorian date (YYYY-MM-DD) to the Bangladesh Bengali calendar, returning Bengali day, month, year, season, and weekday in English and Bengali script.

Instructions

Convert a Gregorian date to the Bangladesh Bengali calendar (Bangla Academy 2019 revision). Returns the Bengali day, month, year, season (ritu) and weekday, in English and 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": {
      "date": "<date>"
    },
    "name": "gregorian_to_bangla"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesGregorian date as YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With readOnlyHint=true already declaring the safe read profile, the description adds real value by enumerating what comes back: Bengali day, month, year, season (ritu), and weekday in both English and Bengali script. It does not cover error behavior for invalid or out-of-range dates, which keeps it short of a 5.

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 tight sentences: the first states the operation and its variant, the second states the return contents. No filler and no repetition of the name.

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 single-parameter read-only conversion tool, the definition covers purpose, calendar variant, and the shape of the result. Since no output schema exists, a brief note on the unit/order of the returned fields would close the last gap.

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?

There is only one parameter and schema coverage is 100%, with the schema itself specifying the YYYY-MM-DD format. The description adds nothing further about the date input, so the baseline of 3 applies.

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?

The description names a specific verb and direction ("Convert a Gregorian date to the Bangladesh Bengali calendar") and pins the calendar revision (Bangla Academy 2019), which unambiguously separates it from the reverse-direction sibling bangla_to_gregorian. An agent can select this tool without opening the schema.

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?

Usage is implied by the conversion direction, and the named revision hints at the variant being used, but there is no explicit statement of when to prefer this over adjacent tools or any preconditions. Adequate but leaves the agent to infer the context.

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