Skip to main content
Glama
bangla-calendar
by FAsami

bd_national_days

Read-only

List Bangladesh's fixed-date national days for a Gregorian year, including weekday and Bengali date. Lunar holidays like the Eids are excluded because they depend on moon sighting.

Instructions

List Bangladesh's fixed-date national days for a Gregorian year, with weekday and Bengali date. Lunar holidays such as the Eids are not included because they depend on moon sighting.

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": {
      "year": "<year>"
    },
    "name": "bd_national_days"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYesGregorian year, e.g. 2027

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

The readOnlyHint=true annotation already establishes this is a safe read, and the description is fully consistent with it. Beyond that, it discloses the shape of the returned data (weekday and Bengali date per day) and the reason for the fixed-date-only scope, which is meaningful added context for a tool with no output schema.

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, front-loaded with the core capability followed by the exclusion rationale. There is no filler, hedging, or redundant restatement of the name.

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?

For a one-parameter, read-only list tool with no output schema, the description covers scope, return content (weekday and Bengali date), and the key behavioral limitation (no lunar holidays). Nothing an agent needs in order to call it correctly is missing.

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 single parameter 'year' is documented as a Gregorian year with an example. The description restates that it is a Gregorian year but adds no format, range, or calendar caveats beyond the schema, so this sits at the baseline.

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 uses a specific verb ('List'), a precisely scoped resource ('Bangladesh's fixed-date national days'), and a bounded input domain ('for a Gregorian year'). It also states what the tool is not (lunar holidays such as the Eids), so an agent can distinguish it from any holiday-adjacent request 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 Guidelines4/5

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

It gives an explicit exclusion rule: lunar holidays such as the Eids are not returned because they depend on moon sighting. That tells the agent when not to rely on this tool, though it does not name a fallback tool for lunar holidays — acceptable since no sibling in the list covers that case.

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