Skip to main content
Glama
Sign In

APIVerve

by com.apiverve
OverviewDiscussionsAdmin

IFSC Lookup

IFSCLookup
Read-only

IFSC Lookup: IFSC Lookup is an IFSC code search API that verifies Indian bank branch details from any IFSC code, returning the bank name, branch, street address, city, district and state, plus the state's ISO code and the bank and branch codes. Paid plans add MICR, SWIFT and the NEFT, RTGS, IMPS and UPI flags. (Cost: 10 credits)

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

Input Schema

NameRequiredDescriptionDefault
ifscYesThe IFSC code to get information about

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNoError message, null on success
statusNo"ok" on success

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, openWorld, non-destructive), and the description adds genuinely new behavior: a 10-credit cost and a plan-tier gate where MICR, SWIFT and NEFT/RTGS/IMPS/UPI flags only appear on paid plans. That conditional-field behavior is exactly the kind of thing an agent cannot infer from annotations or schema. It could go further on failure behavior for invalid codes.

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

Conciseness3/5

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

Dense and front-loaded with the useful content, but the opening redundantly restates the title twice ('IFSC Lookup: IFSC Lookup is an IFSC code search API'), wasting the most valuable position before the actual capability is described.

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 single-parameter read-only lookup with an output schema, the description covers what is needed to call it correctly, plus the credit cost and plan-gated fields. Enumerating return values is somewhat redundant given the output schema, but the plan-tier caveat justifies it.

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% for the single 'ifsc' parameter, so the baseline is 3. The description says 'from any IFSC code' but adds no format, case-sensitivity, or length guidance beyond what the schema already provides.

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?

States a specific verb and resource: verify Indian bank branch details from an IFSC code, and enumerates the returned fields. It does not explicitly distinguish itself from near-neighbours such as SWIFTCodeLookup or RoutingNumberLookup, but the code type named makes the domain clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied rather than stated: call it when you have an IFSC code and want branch details. There is no when-not guidance, no mention of sibling lookups for other code types, and no input validation expectations (format/length).

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

All APIVerve 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