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

india-pincode-ifsc-mcp

by Ankur1911

list_bank_codes

Read-onlyIdempotent

List the 4-letter IFSC bank codes known by name, optionally filtered by text, to find the code needed for search_ifsc.

Instructions

List the 4-letter IFSC bank codes this server knows by name (about 45 larger banks), optionally filtered by text. Use it to find the code for search_ifsc; any other bank's code is the first 4 characters of its IFSC codes.

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

Input Schema

NameRequiredDescriptionDefault
queryNoFilter by part of a bank name or code.

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 declare readOnly, idempotent and openWorld, so safety is covered. The description adds genuinely new behavioral context: the list is name-based and covers only ~45 larger banks, and there is a derivable fallback for everything else. It does not state whether the returned codes are sorted or how names map to codes, keeping it short of a 5.

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?

Two tight sentences with zero filler. The scope limitation is front-loaded, then usage routing, then the fallback rule — an ordering that matches how an agent needs the 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 zero-required-parameter list tool with no output schema, the definition supplies the coverage caveat, the filter behavior and the intended downstream use. The only minor gap is that the shape of the result (name-to-code pairs versus bare codes) is implied rather than stated, though 'codes ... by name' conveys it adequately.

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 'query' parameter is already described as filtering by part of a bank name or code. The description's 'optionally filtered by text' merely restates that at a higher level and adds no matching syntax or edge-case semantics, 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 — listing 4-letter IFSC bank codes — and bounds the scope precisely ('about 45 larger banks'), which prevents the agent from assuming exhaustive coverage. It also names the sibling it serves (search_ifsc), so it is distinguishable without opening another 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?

Explicitly routes the agent: use this tool to obtain the code needed by search_ifsc. It goes further and supplies the fallback rule for banks not in the list ('first 4 characters of its IFSC codes'), covering the when-not case that most definitions omit.

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