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

india-pincode-ifsc-mcp

by Ankur1911

lookup_ifsc

Read-onlyIdempotent

Verify up to 25 IFSC codes in one call and retrieve bank, branch, address, contact, MICR, SWIFT, supported payment services, and PIN details; optionally cross-check the PIN with India Post.

Instructions

Verify and look up 1 to 25 bank IFSC codes in one call (any case or spacing). Each match returns bank, branch, address, city, district, state, phone, MICR, SWIFT and which payment services the branch supports (NEFT, RTGS, IMPS, UPI), plus the PIN code found in the address. Set with_postal_area=true to also look up that PIN with India Post and return its district, state and post offices, which is a quick check that the branch address is consistent. Malformed codes are listed under 'invalid_format' without a request; unknown ones under 'not_found'.

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": {
      "codes": "<codes>"
    },
    "name": "lookup_ifsc"
  }
}

Input Schema

NameRequiredDescriptionDefault
codesYesIFSC codes such as ['HDFC0001069'].
with_postal_areaNoAlso resolve the PIN found in each address via India Post.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld/idempotent, and the description adds substantial behavior beyond that: case/spacing normalization, the 25-code batch ceiling, the full set of returned attributes including supported payment rails, the derived PIN extraction, and how malformed vs. unknown codes are segregated without consuming a request. That is exactly the kind of operational detail an agent needs before calling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core verb, scope, and batch limit, then layered detail on returns and error buckets. The return-attribute enumeration is dense but justified given there is no output schema; nothing reads as filler, though the sentence is long.

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?

With no output schema, the description fully covers return shape, the optional enriched return path, and error partitioning, while annotations cover the safety profile. Nothing material for correct invocation 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 the baseline is 3, but the description adds real meaning: 'codes' accepts any case or spacing (normalization not stated in the schema), and 'with_postal_area' is characterized not just as an extra lookup but as an address-consistency check with its own returned fields.

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?

The description names a specific verb and resource ('Verify and look up ... bank IFSC codes') plus the batch scope ('1 to 25 ... in one call'). It implicitly separates itself from siblings like search_ifsc by framing the operation as exact-code validation with 'invalid_format'/'not_found' buckets, though it never names an alternative outright.

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: use it for bulk verification of known codes, and set with_postal_area=true when you want to cross-check a branch address against India Post data. No explicit when-not-to-use or named alternative (e.g. search_ifsc for name-based lookup) is provided.

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