Skip to main content
Glama

Ifsc Lookup

ifsc_lookup
Read-onlyIdempotent

Indian bank branch lookup by IFSC code. Resolves an 11-character IFSC code (printed on Indian cheques and bank statements) to the bank name, branch, address, city, district, state, MICR code, SWIFT code, and contact number, plus whether the branch supports the NEFT, RTGS, UPI, and IMPS payment rails. India banking / fund-transfer routing data via the open Razorpay IFSC dataset (keyless). Also returns an offline format_valid check of the code structure. NOTE: this validates and resolves the IFSC code itself, it does NOT verify a bank account or account holder. Examples: ifsc_lookup({ ifsc: "HDFC0CAGSBK" }), ifsc_lookup({ ifsc: "sbin0000691" }) (case and spaces are forgiven).

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ifsc": "HDFC0CAGSBK"
    },
    "name": "ifsc_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
ifscYesThe 11-character IFSC code, e.g. "HDFC0CAGSBK" or "SBIN0000691". Format: 4 letters (bank) + 0 + 6 alphanumerics (branch). Spaces and lowercase are tolerated.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "ifsc": "HDFC0CAGSBK"
      +  },
      +  {
      +    "ifsc": "sbin0000691"
      +  }
      +]
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered elsewhere. The description does add genuinely useful context beyond them: the keyless Razorpay IFSC dataset as the source (implying no auth), the full set of returned fields, and the offline 'format_valid' structural check. It does not say how malformed or unresolvable codes are reported (error vs. partial result), which is the main remaining behavioral gap.

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?

The purpose and scope come first, with the caveat and examples afterward — correct front-loading. The two trailing example invocations duplicate the schema's own 'examples' array and add little, keeping it from a 5, but nothing is buried or redundant within the prose itself.

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?

For a one-parameter read-only lookup with no output schema, the definition supplies the return-field inventory, the data source and its keyless nature, the format_valid check, and the account-verification caveat. An agent has everything needed to decide to call it and to interpret the result.

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 coverage is 100% and the single parameter already documents the 4-letters + 0 + 6-alphanumerics structure and its tolerance for spaces and lowercase. The description restates the same tolerance and adds worked examples, but no meaning beyond what the schema supplies. With full schema coverage, the baseline of 3 applies.

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 opening sentence gives a specific verb and resource ('Indian bank branch lookup by IFSC code'), then 'Resolves an 11-character IFSC code ... to the bank name, branch, address, city, district, state, MICR code, SWIFT code, and contact number' enumerates exactly what comes back. It also draws a hard scope boundary ('does NOT verify a bank account or account holder'), so an agent can tell precisely what question this tool answers.

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 states the use case (routing data for Indian bank branches) and an explicit exclusion — validation of the code, not of an account or holder — which is the most plausible mistaken use. It even clarifies input tolerance ('case and spaces are forgiven'). It stops short of naming any alternative tool, though with one parameter and no comparable sibling that omission is low-cost.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.