Skip to main content
Glama

Japan Public Data (法人番号・登録支援機関・官公需入札)

Lookup Japanese corporate number

lookup_corporate_number
Read-onlyIdempotent

Look up Japanese companies in the National Tax Agency Corporate Number Publication Site. Search by 13-digit corporate number, or by company name. Returns name, address and status. 国税庁 法人番号公表サイトから、法人番号(13桁)または法人名で法人情報(名称・所在地・閉鎖有無)を検索します。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "lookup_corporate_number"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoCompany name, partial match, closed companies excluded / 法人名(部分一致・閉鎖法人は対象外)。number とは同時指定不可
numberNo13-digit corporate number / 法人番号(13桁)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new behavior context: it names the authoritative source and enumerates the returned fields (name, address, status), which matters because there is no output schema. It stops short of noting rate limits or that name search excludes closed companies (that caveat lives only in the schema).

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 content is front-loaded and the English sentences are tight — purpose, two search modes, and return fields in three sentences. The full Japanese restatement doubles the length without adding new information, which is a minor cost to conciseness.

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?

With only two optional parameters and no output schema, the description supplies what the structured fields do not: the data source and the shape of the result. The one gap is the unstated rule that name and number cannot be combined, which is relevant to correct invocation.

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 description coverage is 100%, so the schema already documents both parameters including the 13-digit constraint and the partial-match/exclusion behavior for name. The description restates the 13-digit format and both search modes but adds no syntax or semantics beyond the schema; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb ('Look up') tied to a concrete resource (Japanese companies in the NTA Corporate Number Publication Site) and names both search modes. It does not explicitly contrast itself with siblings like search_local_govt_bids, but the domain is distinct enough that confusion is unlikely.

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?

'Search by 13-digit corporate number, or by company name' implies when each input is appropriate, but there is no explicit when-to-use/when-not guidance. Critically, the mutual exclusivity of name and number — documented in the schema — is not surfaced in the description, so an agent skimming only the description could attempt both.

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.