Skip to main content
Glama
bangladesh-mcp

bangladesh-mcp

by sarif-mia

check_mobile_numbers

Read-onlyIdempotent

Validate Bangladeshi mobile numbers in any common format, normalize them to +880, and identify the operator—including Bangla digits.

Instructions

Validate Bangladeshi mobile numbers, normalise them to +880 format and detect the operator.

Args: numbers: Numbers in any common format, e.g. "01712-345678", "+880 1912 345678", Bangla digits.

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": {
      "numbers": "<numbers>"
    },
    "name": "check_mobile_numbers"
  }
}

Input Schema

NameRequiredDescriptionDefault
numbersYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish the safe read-only, idempotent, closed-world profile, so the description's job is to add operational detail — and it does, disclosing that output includes both a normalised +880 form and a detected operator. The notable omission is behaviour on invalid or foreign numbers (error vs. per-item failure vs. silent skip), which matters for a batch 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?

Two tight sentences with the core action front-loaded, followed by a compact Args block that carries only useful format examples. Nothing is redundant with the schema or annotations, and there is no filler.

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?

With rich annotations and an output schema present, the description need not explain return structure, and it correctly focuses on input formats and the transformation performed. The remaining gap is failure semantics for invalid or partially-invalid input lists, which an agent would want before calling this on a batch.

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 0% — the schema says only 'array of strings, title Numbers' — so the description must compensate, and it does with concrete accepted-format examples including Bangla digits. It stops short of clarifying that the argument is a list of many numbers processed together (the examples read as single values), leaving batch semantics to inference.

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 opens with a specific verb-plus-resource statement and enumerates three concrete operations: validating Bangladeshi mobile numbers, normalising to +880 format, and detecting the operator. That is enough to separate it from the sibling arithmetic/conversion utilities without opening any 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 input-format examples (Bangla digits, dashed, spaced, +880 prefixed), which tell an agent this is the tool for messy local number input. However, there is no explicit statement of when not to use it, no note about non-Bangladeshi numbers, and no named alternative for related digit-conversion needs despite a convert_digits sibling.

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