Skip to main content
Glama

Japan Business ID

Validate a Japanese invoice registration number

validate_invoice_number
Read-onlyIdempotent

Check a Japanese qualified invoice registration number (適格請求書発行事業者登録番号, "T" + 13 digits) for format and check digit, tell whether it is a corporation's number, and return the official lookup URL. Accepts full-width characters and hyphens.

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_invoice_number"
  }
}

Input Schema

NameRequiredDescriptionDefault
numberYese.g. T8700110005901

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world behavior, so the description's job is to add what they can't. It does: format plus check-digit validation, corporation classification, an official lookup URL in the response, and tolerance for full-width characters and hyphens. It does not say what happens on an invalid number (error vs. a false validity flag), which keeps it from a 5.

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 tightly packed sentence with the resource and format front-loaded, followed by the checks and outputs. Every clause carries information: format rules, check-digit verification, corporation flag, lookup URL, and accepted input variants. No filler or restatement of the title.

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, read-only validator with no output schema, the description covers inputs (accepted character variants) and outputs (validity, corporation flag, lookup URL) well. The one gap is failure semantics for an invalid number, which matters for a tool whose whole purpose is rejection.

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% and the property already carries an example, so baseline is 3. The description earns an extra point by stating that full-width characters and hyphens are accepted, which is input normalization guidance the schema's plain string type and maxLength never convey.

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 (check) against a precisely identified resource, including the exact format ('T' + 13 digits) and the two checks performed (format and check digit). The extra behavior — corporation determination and official lookup URL — makes it distinguishable from validate_corporate_number and extract_business_ids without opening a schema.

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 narrow scope (validating invoice registration numbers), but the description never says when to prefer this over validate_corporate_number or when to combine it with extract_business_ids. No exclusions or prerequisite context are offered, leaving routing to the agent's inference.

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.