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

india-pincode-ifsc-mcp

by Ankur1911

search_ifsc

Read-onlyIdempotent

Find bank branches and their IFSC codes by filtering on bank, city, or branch name; use paging to retrieve additional results.

Instructions

List bank branches and their IFSC codes, filtered by bank, city and/or branch name (at least one filter). 'bank' accepts a 4-letter bank code or a well-known name such as 'HDFC Bank', 'SBI' or 'Kotak'. City and branch names are matched exactly as the dataset spells them (for example 'MUMBAI', 'SAROJINI NAGAR'), so an unlisted spelling returns nothing. Results are paged: when more exist the reply has next_offset to pass back as offset. For one known IFSC use lookup_ifsc.

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": "search_ifsc"
  }
}

Input Schema

NameRequiredDescriptionDefault
bankNoBank code ('HDFC') or name ('Punjab National Bank', 'SBI').
cityNoCity exactly as the dataset spells it, e.g. 'PUNE'.
limitNoBranches per page.
branchNoBranch name, e.g. 'ANDHERI'.
offsetNoSkip this many results (use next_offset from the previous reply).

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?

Annotations already cover the safety profile (readOnly, idempotent, open-world), and the description adds real operational context beyond them: exact-string matching against the dataset that yields empty results rather than fuzzy hits, plus the paging contract where next_offset is fed back as offset. It stops short of describing the shape of each branch record, which is the only notable omission.

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?

Three sentences, front-loaded with purpose and filters, then the matching caveat, then the paging rule and the sibling pointer. No filler and no sentence that could be dropped 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 five-parameter, read-only search tool with no output schema, the description covers purpose, filter semantics, matching pitfalls, pagination, and the alternative tool. A brief note on what each returned branch record contains (beyond the IFSC code) is the only gap, and it is minor given the tool's simplicity.

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?

Schema description coverage is 100%, so every one of the five parameters is already documented, including the bank code-or-name duality and the offset/next_offset convention. The description largely restates that content with example values, adding emphasis rather than new meaning; baseline 3 is appropriate.

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 ('List bank branches and their IFSC codes') plus the filtering dimensions (bank, city, branch). It also explicitly distinguishes itself from lookup_ifsc for the single-record case, so an agent can choose between the two without opening 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?

It gives an explicit precondition ('at least one filter'), a spelling-mismatch warning that explains the failure mode ('an unlisted spelling returns nothing'), and names the sibling to use instead for a single known IFSC. That is when-to-use, when-not-to-use, and the alternative in three sentences.

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