AgentStall: Africa and global data for agents

India IFSC code lookup: bank, branch, address, MICR and UPI/NEFT/RTGS/IMPS support

india_ifsc_lookup

Read-onlyIdempotent

IFSC code lookup for Indian bank branches: returns the bank, branch name, address, city, district, state, MICR code, SWIFT code where available, and whether the branch supports NEFT, RTGS, IMPS and UPI. Covers all banks in India including SBI, HDFC Bank, ICICI Bank, Axis Bank and co-operative banks, from the open Razorpay IFSC dataset built on RBI and NPCI lists. Useful for validating Indian bank transfer details before a payout. Price: $0.001 USDC per call (x402, Base mainnet).

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": {
      "ifsc": "<ifsc>"
    },
    "name": "india_ifsc_lookup"
  }
}

Input Schema

Name	Required	Description	Default
`ifsc`	Yes	11-character IFSC code, e.g. HDFC0000001 or SBIN0000300

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds genuine context beyond that: it discloses the price ($0.001 USDC per call via x402 on Base mainnet) and the data provenance (Razorpay IFSC dataset over RBI/NPCI lists). It says nothing about not-found behavior, error modes, or response shape.

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?

Single front-loaded paragraph that leads with the return payload, then coverage, then provenance, then price — a sensible ordering. The SBI/HDFC/ICICI/Axis bank list is mildly padded but does signal breadth of coverage, so it earns its place.

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 one-parameter lookup with no output schema, the description does the heavy lifting by enumerating returned fields, stating coverage and provenance, and disclosing per-call cost. What is missing is behavior on an invalid or unknown IFSC, which an agent would need to interpret results correctly.

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% and the schema already specifies the 11-character IFSC format with examples (HDFC0000001, SBIN0000300). The description adds no further meaning about the parameter, so 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?

States a specific verb and resource ("IFSC code lookup for Indian bank branches") and enumerates exactly what is returned: bank, branch, address, city, district, state, MICR, SWIFT, and NEFT/RTGS/IMPS/UPI support flags. The India/IFSC scoping cleanly separates it from the country-specific sibling za_bank_branch_codes without needing to open 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 Guidelines4/5

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

Gives a concrete use case — "validating Indian bank transfer details before a payout" — which tells the agent which task class to route here. It stops short of naming a when-not condition or pointing to alternatives, so it is clear context without exclusions.

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

All AgentStall: Africa and global data for agents tools Inspect

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

Need Help?