Skip to main content
Glama

Japan Bank Code

Find a Japanese bank branch code

lookup_branch
Read-onlyIdempotent

Find a branch of a Japanese bank by 3-digit branch code (支店コード) or by branch name / kana.

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": "<bank>",
      "query": "<query>"
    },
    "name": "lookup_branch"
  }
}

Input Schema

NameRequiredDescriptionDefault
bankYes4-digit bank code or exact bank name
queryYesBranch code or name, e.g. 001, 東京営業部, シブヤ

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and closed-world behavior, so the safety profile is covered. The description adds nothing behavioral beyond the schema: it does not say whether an ambiguous name can return multiple branches, whether results are truncated, or whether exact-match is required. Adequate but with clear gaps given how little it contributes on top of the annotations.

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?

A single front-loaded sentence with no filler; the resource and both accepted key formats are stated immediately. Nothing would be gained by trimming it further.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read-only lookup with full schema coverage this is close to sufficient, but with no output schema the description should say what a hit looks like (branch name, address, code, or a list on ambiguous names). That single missing detail is the only material gap.

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%, with both 'bank' (4-digit code or exact name) and 'query' (branch code, 東京営業部, シブヤ) fully documented in the schema itself. The description only echoes the query formats and adds the 支店コード label; it does not clarify constraints such as case/kana normalization or what happens with partial matches. Baseline 3 is appropriate.

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?

The description names a specific verb and resource ('Find a branch of a Japanese bank') and enumerates the two lookup keys (3-digit branch code / 支店コード or branch name/kana). This is clearly distinguishable from a bank-level lookup, though the description never names or contrasts the bank-level sibling explicitly.

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 by the phrasing 'by branch code ... or by branch name', which tells the agent the two acceptable query modes. However, there is no when-to-use versus when-not guidance and no mention of alternatives such as verify_bank_branch or a bank-name lookup path before this one.

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.