Skip to main content
Glama
india-pincode-ifsc-mcp

india-pincode-ifsc-mcp

by Ankur1911

lookup_pincodes

Read-onlyIdempotent

Validate and look up 1–25 Indian PIN codes in one call, returning state, district, division, region, postal circle, and post offices with office type and delivery status.

Instructions

Validate and look up 1 to 25 Indian PIN codes in one call. Each match returns state, district, division, region, postal circle and the post offices under that PIN with their type (HO head, SO sub, BO branch office) and whether they deliver mail. PINs that are not 6 digits are reported under 'invalid_format' without a request; well-formed PINs that India Post does not know are under 'not_found'. detail='full' adds each office's block and raw fields. Use search_post_offices when you only have a locality name.

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": {
      "pincodes": "<pincodes>"
    },
    "name": "lookup_pincodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailNo'summary' (default) lists office names compactly.summary
pincodesYesPIN codes such as ['110001', '560001'].

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, openWorld), yet the description still adds real behavior: short-circuited validation (malformed PINs land in 'invalid_format' without a request), a distinct 'not_found' bucket for well-formed but unknown PINs, and the per-match payload fields. It stops short of noting rate limits or whether the underlying lookup is cached, so it is strong but not exhaustive.

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?

Four sentences, front-loaded with the core operation, then output shape, then error buckets, then the alternative-tool routing. Every clause carries information an agent needs; nothing is redundant with the schema.

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?

There is no output schema, and the description compensates by enumerating returned fields, the office-type codes (HO/SO/BO), delivery status, and both failure categories. For a two-parameter batch-read tool with annotations covering safety, nothing material is missing.

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 100%, so baseline is 3, but the description adds meaning the schema lacks: what detail='full' actually contributes (office block and raw fields) versus the compact summary, and the 6-digit format expectation implied by the 'invalid_format' bucket. The enum only explains 'summary', so this genuinely supplements it.

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?

States a specific verb pair ('validate and look up'), the exact resource ('Indian PIN codes'), and the batch bound ('1 to 25 ... in one call'). It also names the sibling it is not ('search_post_offices') so an agent can separate the two without reading either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives an explicit routing rule with its condition: use search_post_offices when you only have a locality name, which implies lookup_pincodes is for when you already hold PIN strings. The 1-25 batch constraint further frames appropriate use.

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