Skip to main content
Glama

Japan Bank Code

Find a Japanese bank code

lookup_bank
Read-onlyIdempotent

Find a Japanese financial institution by 4-digit bank code (金融機関コード) or by name in kanji, kana (full or half width) or romaji. Covers banks, shinkin, credit unions, JA and more.

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": {
      "query": "<query>"
    },
    "name": "lookup_bank"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesBank code or name, e.g. 0001, みずほ, ミズホ, mizuho

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/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 what annotations cannot: that lookups tolerate multiple writing systems and widths, implying normalization and transliteration on input. It does not say what happens on a miss, what is returned, or how a partial name match behaves.

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 sentences, no filler, with the primary lookup mode and identifier format front-loaded. The coverage sentence adds real scope information rather than restating the title.

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, read-only, closed-dataset lookup with full annotations, the description supplies everything needed to call it correctly, including input formats. The remaining gap is that there is no output schema and the description does not indicate the shape of the result, so the agent cannot tell whether parts of an address are returned or multiple matches are possible.

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% and the single parameter already carries examples (0001, みずほ, ミズホ, mizuho), so the baseline is 3. The description earns extra credit by noting that the same parameter accepts kanji as well as full-width and half-width kana and romaji, which explains the schema's mixed examples better than the schema does.

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-plus-resource: find a Japanese financial institution by 4-digit bank code or by name. It names the identifier format (金融機関コード) and the accepted scripts, so an agent can immediately tell this is an institution-level lookup, not a branch lookup. It does not explicitly contrast with lookup_branch or verify_bank_branch, but the resource phrasing already makes the distinction.

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 clear context for when to use: any bank code, or any name written in kanji, kana (full or half width) or romaji. The coverage sentence ('Covers banks, shinkin, credit unions, JA and more') tells the agent how far the dataset extends, which helps it decide whether to reach for a different tool. It does not state explicit exclusions or name alternative tools.

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.