Skip to main content
Glama

Find corporate numbers by name / 法人の名前から法人番号

search_corporation_by_name
Read-onlyIdempotent

Find Japanese corporations whose name starts with the given text (prefix match), in the National Tax Agency's monthly bulk data. Legal-form words such as 株式会社 or 一般社団法人 are ignored at either end, and full/half-width and spaces are normalized. Matching in the middle of a name and furigana search are not supported. flags: truncated, exact_match_only (too many names start with the input; only exact matches returned), not_found. Returns up to 100 matches (total, returned, truncated) with corporate number, name, prefecture, city and is_closed (registry record closed); use lookup_corporate_number for details. Corporations marked as excluded from search on the NTA site are not included. / 名前の先頭が合う法人を探します(前方一致)。「株式会社」などの言葉は、名前の前後どちらにあっても無視し、全角・半角や空白の違いも吸収します。名前の途中からの検索と、フリガナでの検索はできません。最大100件を返します。詳しい情報は、lookup_corporate_number で調べてください。国税庁のサイトで「検索対象除外」とされた法人は、含まれません。

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

Input Schema

NameRequiredDescriptionDefault
nameYesBeginning of the corporate name (e.g. トヨタ自動車) / 法人の名前の先頭(例:トヨタ自動車)
prefectureNoPrefecture to narrow down (optional, e.g. 東京都 or 東京) / 都道府県で絞り込む(任意)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / name / maxLength
      Added value: +200
    • addedInput schema / properties / prefecture / maxLength
      Added value: +200
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover read-only and idempotent behavior, yet the description adds real operational context: normalization of legal-form words, full/half-width and spaces, a 100-match cap, and the meaning of the truncated, exact_match_only and not_found flags. It also discloses a data limitation (NTA-excluded corporations are absent) and that is_closed marks a closed registry record.

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?

Content is front-loaded and dense with no filler, but the full English/Japanese duplication roughly doubles the length; an agent only needs one language. Each clause still carries information, so it stops short of being verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description takes on the job of explaining return values (total, returned, truncated, corporate number, name, prefecture, city, is_closed) and the result cap. Nothing an agent needs in order to call this correctly or interpret the response is missing.

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%, so baseline is 3, but the description adds genuine semantics for the name parameter: it is a prefix match, legal-form tokens at either end are stripped, and width/space differences are normalized. Prefecture is not elaborated beyond the schema, which keeps it from a 5.

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 verb and resource (find Japanese corporations by name prefix) plus the data source (NTA monthly bulk data). It distinguishes itself from lookup_corporate_number, which it routes to for detail, so an agent can tell the two apart without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-not conditions are given: middle-of-name matching and furigana search are unsupported, and the description recommends lookup_corporate_number for details once a candidate is found. It also discloses the exact_match_only fallback, so the agent knows how the tool degrades under broad input.

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.

Resources