Skip to main content
Glama

Japan Business ID

Corporate number from registry number

corporate_number_from_base
Read-onlyIdempotent

Build the 13-digit corporate number (法人番号) from a 12-digit company registry number (会社法人等番号) by computing the check digit.

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": {
      "base_number": "<base_number>"
    },
    "name": "corporate_number_from_base"
  }
}

Input Schema

NameRequiredDescriptionDefault
base_numberYes12-digit 会社法人等番号

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, and closed-world behavior, so the safety profile is covered. The description adds that the transformation is a deterministic check-digit computation, which is useful, but it says nothing about behavior on malformed input (e.g., non-12-digit strings) or the type of the returned value.

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, front-loaded with the output, with zero redundant wording. Both the Japanese and English names are given, which aids disambiguation.

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 trivial pure-computation tool with no output schema, the description tells the agent exactly what comes back (a 13-digit corporate number) and how it is derived. Only input-validation behavior is unaddressed, a minor gap against the annotations that already cover the safety profile.

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 parameter is already documented as the 12-digit 会社法人等番号. The description restates the 12-digit requirement but adds no new detail such as accepted formats or validation errors, 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: build the 13-digit 法人番号 from a 12-digit 会社法人等番号 by computing the check digit. The transformation direction and Japanese terminology make it clearly distinct from validate_corporate_number, which cannot be confused with a construction operation.

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 input/output description (use when you hold a 12-digit registry number and need the 13-digit corporate number), but there is no explicit when-to-use/when-not statement and no sibling is named. An agent can infer the call site, but guidance is only implicit.

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.