Skip to main content
Glama

Japan Business ID

Validate a Japanese corporate number

validate_corporate_number
Read-onlyIdempotent

Check a Japanese corporate number (法人番号, 13 digits) with the National Tax Agency check digit formula; on a typo, return the expected check digit. Returns the official lookup URL.

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

Input Schema

NameRequiredDescriptionDefault
numberYes13-digit corporate number, e.g. 8700110005901

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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; the description adds real value beyond them by disclosing the checksum algorithm, that a typo yields the expected check digit, and that the official lookup URL is returned. It also implicitly confirms no external existence lookup is performed, consistent with openWorldHint=false.

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 tight clauses, front-loaded with the core action and the standard used, with the error behavior and return value appended. There is no redundancy or filler.

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, annotation-covered tool with no output schema, the description covers purpose, algorithm, error behavior and one return value (lookup URL). The exact response shape for the success case (e.g. a boolean valid flag) is not stated, which is the only remaining 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 coverage is 100% and the single parameter already carries its format and an example (8700110005901). The description only echoes the '13 digits' constraint, adding no syntax or normalization guidance beyond the schema, so the baseline 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?

The description names a specific action (check/validate) applied to a specific resource (Japanese corporate number, 13 digits) and cites the exact standard used (National Tax Agency check digit formula). This makes it immediately distinguishable from siblings like validate_invoice_number or extract_business_ids.

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 name and by the checksum-based purpose, but there is no explicit statement of when to prefer this over the sibling validators or what to do for non-Japanese numbers. No exclusions or preconditions are given, so an agent must infer the boundary.

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.