Skip to main content
Glama

Japan Bank Code

Verify a bank and branch code pair

verify_bank_branch
Read-onlyIdempotent

Before a domestic bank transfer, check that a bank code + branch code pair exists and return the official names and kana (as used in zengin transfer files).

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": {
      "bank_code": "<bank_code>",
      "branch_code": "<branch_code>"
    },
    "name": "verify_bank_branch"
  }
}

Input Schema

NameRequiredDescriptionDefault
bank_codeYes4 digits
branch_codeYes3 digits

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 real domain context by saying the returned kana is what appears in zengin transfer files, but it never states what happens when the pair does not exist (error vs. a not-found result), which is the key behavioral question for a verification tool.

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?

One sentence that front-loads the trigger, then the action, then the return value, with no filler. A slightly crisper split of action versus return content would make it a 5, but nothing here is wasted.

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?

With only two fully documented parameters and no output schema, the description does the important extra work of saying what comes back (official names and kana). The remaining gap is the not-found behavior, which matters for a verification call but is a small omission given how thin this tool is.

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 schema already states '4 digits' and '3 digits' for the two fields. The description adds no format, validation, or normalization detail beyond what the schema provides, so the baseline of 3 applies.

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 (check/verify), a specific resource (a bank_code + branch_code pair), and the intended moment of use (before a domestic bank transfer). The wording about the 'pair' implicitly differentiates it from the single-field siblings lookup_bank and lookup_branch, though it never names them.

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 trigger condition is explicit and useful: run this before a domestic bank transfer. It does not state when to prefer lookup_bank or lookup_branch, nor what to do if the caller only has one of the two codes, so the alternative-selection guidance is incomplete.

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.