Skip to main content
Glama

Ifsc In

by io.github.pipeworx-io
OverviewDiscussionsAdmin

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).

Input Schema

TableJSON 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.7/5.0
Behavior5/5

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

Annotations already indicate readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false. The description adds that the data comes from the open Razorpay IFSC dataset (keyless) and that it returns an offline format_valid check. It also clarifies that it does NOT verify accounts, adding significant behavioral context beyond annotations.

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?

The description is concise (3-4 sentences) and front-loaded with the main purpose. Examples are included for clarity. Every sentence adds value without redundancy.

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?

Given a single parameter and no output schema, the description lists all return fields (bank name, branch, address, city, district, state, MICR, SWIFT, contact, payment rails) and mentions the format_valid check. This provides complete context for the tool's output.

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% with detailed description of the IFSC parameter (format, tolerance for spaces/lowercase). The description adds example calls and confirms case/space forgiveness, which aids understanding beyond the schema.

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 clearly states the tool resolves an 11-character IFSC code to bank details including branch, address, city, state, MICR, SWIFT, contact, and payment rail support. It uses a specific verb 'lookup' and resource 'bank branch', and among sibling tools, none overlap with this function.

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?

The description explicitly says when to use the tool (for IFSC code lookup) and notes that it does not verify bank accounts or account holders, which helps avoid misuse. While it doesn't list alternative tools, no relevant alternatives exist among siblings.

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

All Ifsc In toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources