Skip to main content
Glama
bangla-calendar
by FAsami

bd_mobile_number

Read-only

Validate Bangladeshi mobile numbers in common formats, identify the operator, and return normalized forms for consistent storage or verification.

Instructions

Validate a Bangladeshi mobile number in any common format and return its operator (Grameenphone, Banglalink, Robi, Airtel, Teletalk) and normalised forms.

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": {
      "number": "<number>"
    },
    "name": "bd_mobile_number"
  }
}

Input Schema

NameRequiredDescriptionDefault
numberYesMobile number, e.g. 01712-345678 or +8801712345678

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?

readOnlyHint=true already tells the agent this is a safe, non-mutating call, so the description's job is lighter; it still adds real value by enumerating the five possible operators and promising normalised output forms. The notable omission is what happens on an invalid number — whether the call errors or returns a negative result — which is central for a validator.

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?

A single tight sentence with zero filler; the action, resource, and return values are all front-loaded. Nothing could be cut without losing information.

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 one-parameter, read-only lookup with no output schema, the description does the important work of naming the return values (operator from a closed list, normalised forms) so the agent need not guess. Only the failure/invalid-input semantics remain undescribed.

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?

With one parameter and 100% schema description coverage, the schema already documents the field and gives two example formats, so the baseline is 3. 'Any common format' broadens the accepted-input expectation slightly but adds no format rules (length, leading zero vs +880, separators) beyond the examples.

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?

States a specific verb and resource ('Validate a Bangladeshi mobile number') plus the returned artifacts (operator, normalised forms), so the agent knows exactly what the tool does. It does not explicitly contrast itself with siblings such as to_bangla_digits or bd_district, though there is no realistic intent overlap.

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 only implied: an agent can infer it should call this when it needs to check a BD mobile number or identify its operator. There is no explicit when-to-use, when-not-to-use, or statement that format normalisation alone should go to a different tool.

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