Skip to main content
Glama

日本の給与・社会保険・労働法

by io.github.kishida-devil

インボイス登録番号をまとめて形式検査

validate_invoice_numbers_batch

Checks the National Tax Agency check digit on many qualified-invoice registration numbers in one call.

Be careful how you report the result. A passing check digit means the shape of the number is right and nothing more. 消費税法第57条の2 provides both for the Commissioner to revoke a registration and for one to lapse, so a well-formed number can be unregistered, revoked or expired. Never tell someone a number is valid, verified or confirmed on the strength of this — say the format checks out, and that the register itself was not consulted.

What it does earn is elimination. Anything failing on shape needs no lookup at all, so the list taken to 国税庁「適格請求書発行事業者公表サイト」 gets shorter. That site publishes the revocation and lapse dates, and offers a bulk download and a Web-API for large lists.

Duplicates come back as given rather than folded together, and each result carries the index of its input, so rows line up with the caller list they came from.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
numbersYesRegistration numbers as written, including the leading T. Up to 1000 per call.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations provided, the description fully carries the behavioral disclosure burden. It explicitly warns that a passing check digit does not mean the number is registered, explains revocation/lapse possibilities, says the register is not consulted, and details duplicate and index behavior. This is unusually transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is longer than average, but it front-loads the core function in the first sentence and organizes the rest into crucial caveats, workflow value, and result behavior. Each section earns its place, though the detail about the public site's bulk download and Web-API is somewhat tangential.

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 tool with no output schema, the description covers the important context: what the check does and does not prove, how results are keyed, and how duplicates behave. It does not specify the exact return payload shape, but it gives enough behavioral detail for an agent to call it and interpret results safely.

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?

The only parameter, 'numbers', is already fully described in the schema with the leading T requirement and the 1000-per-call limit, so schema coverage is 100%. The description adds no new parameter-level meaning beyond what the schema already states, making the baseline 3 appropriate.

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 states a specific action (checks the National Tax Agency check digit) on a specific resource (qualified-invoice registration numbers) in batch, and clearly differentiates this from the sibling validate_corporate_number tool by targeting invoice registration numbers specifically. The title also reinforces the batch scope.

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?

The description gives clear workflow context: use this to filter out numbers that fail format checks before consulting the official register, and explains why the actual register must be consulted for real validity. It does not explicitly name alternative sibling tools or state 'when not to use', so it stops short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All 日本の給与・社会保険・労働法 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation4/5

Most tools have distinct, well-defined jobs—payroll calculations, revision judgments, eligibility checks, and data lookups are clearly separated. The main remaining risk is among the standard-remuneration judgment tools and the batch/singleton pairs, but their descriptions are detailed enough to prevent serious misselection.

Naming Consistency3/5

There is a reasonably recognizable pattern with calculate_, judge_, check_, get_, and validate_ groups. However, several noun-phrase names (business_days, consumption_tax, national_insurance, commuting_allowance_exemption) and overlapping verb choices (decide_ vs judge_ vs check_) prevent a fully consistent verb_noun convention.

Tool Count2/5

At 30 tools, the surface is materially larger than the 3–15 range that keeps an agent's selection burden low. Batch variants and three separate standard-remuneration revision tools add complexity, and although the domain is broad, the count feels heavy for an assistant to choose from confidently.

Completeness4/5

The core workflows are well covered: monthly pay, bonuses, overtime, standard-remuneration determination, year-end adjustment, resident tax, leave, worker classification, and invoice validation. Gaps exist around statutory benefit payments such as sickness or maternity allowances and retirement-specific processing, but most payroll and social insurance tasks can be completed without dead ends.

Resources