Skip to main content
Glama
bangla-calendar
by FAsami

bd_district

Read-only

Look up a Bangladeshi district and its division, with support for old spellings like Comilla and Chittagong. Omit the name to list all 64 districts grouped by division.

Instructions

Look up a Bangladeshi district and its division. Accepts old spellings (Comilla, Jessore, Bogra, Chittagong, Barisal). Leave name empty to list all 64 districts by division.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "bd_district"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoDistrict name; omit to list all districts

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?

The readOnlyHint annotation already establishes that this is a safe lookup. The description adds useful behavior beyond annotations by noting accepted old spellings and that an empty name returns all 64 districts grouped by division. It leaves some edge cases, such as unknown names or matching rules, unspecified.

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?

The definition is two concise sentences, front-loaded with the core purpose and followed by practical input guidance. Every sentence contributes useful information without repetition.

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 simple one-parameter lookup tool with readOnlyHint and no output schema, the description covers purpose, alias handling, and empty-input behavior. It is nearly complete, though it does not specify matching rules or what happens for an unrecognized district name.

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 already 100%, so the schema documents the single parameter. The description adds meaningful semantics beyond the schema by listing old spelling aliases and reinforcing the empty-name listing behavior.

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 states a specific verb and resource: 'Look up a Bangladeshi district and its division.' It is immediately clear what the tool returns and is unambiguous against the unrelated sibling tools.

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 clear usage context, including that the name may be omitted to list all districts. It does not explicitly name alternatives, but none of the sibling tools perform this lookup, so the guidance is sufficient.

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