Skip to main content
Glama

Japan Bank Code

Japan Post Bank number to transfer details

yucho_to_transfer
Read-onlyIdempotent

Convert a Japan Post Bank (ゆうちょ銀行) 記号・番号 into the branch name, branch code, account type and account number needed to receive transfers from other banks, using the official rule (e.g. 11940-12345671 -> 198 一九八店 普通 1234567). Nothing is stored.

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": {
      "symbol": "<symbol>",
      "number": "<number>"
    },
    "name": "yucho_to_transfer"
  }
}

Input Schema

NameRequiredDescriptionDefault
numberYes番号, up to 8 digits
symbolYes記号, 5 digits

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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 safety is covered. The description adds that the mapping follows 'the official rule' (deterministic) and that 'Nothing is stored' (stateless), but says nothing about failure behavior for malformed or unknown 記号 values, which matters for a pure converter.

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?

One sentence, the example inline, and a short statelessness note — purpose is front-loaded with zero padding. Nothing could be removed without losing meaning.

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?

There is no output schema, so the description must convey return values, and it does — branch name, branch code, account type, account number, plus a formatted sample output. Only the exact response shape (field names, separators, full-width vs half-width numerals) is left unspecified.

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%, so the baseline is 3; the description earns above baseline by showing a concrete input instance whose two components ('11940' and '12345671') map onto the two required parameters, clarifying how 記号 and 番号 combine into the conversion.

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 precise verb and resource: convert a Japan Post Bank 記号・番号 into branch name, branch code, account type and account number. The worked example (11940-12345671 -> 198 一九八店 普通 1234567) makes the input/output relationship unambiguous and implicitly separates it from the generic lookup_bank / lookup_branch siblings.

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 a clear use case: obtaining the details 'needed to receive transfers from other banks', which tells the agent the triggering situation. It does not name alternatives (e.g. lookup_branch) or state when not to use it, so it stops short of full routing guidance.

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.