Skip to main content
Glama

法人番号・会社名から会社情報を調べる

lookup_company
Read-only

法人番号または会社名から、gBizINFO(経済産業省の法人情報サイト)の会社情報を読み込む。保存はしない。

    会社情報を聞き取る前に使うと、利用者は「確認するだけ」で済む。
    name(会社名。prefecture に都道府県名を添えると絞れる)では候補の一覧(法人番号・名称・所在地)を返す。
    どの会社かを利用者に確かめてから、corporate_number(13桁)で呼ぶ。
    corporate_number では次を返す。proposed は save_company_profile の company にそのまま足せる項目と値。
    differences は今の会社情報と違う項目(今の値・gBizINFO の値)で、今の値がある項目は、利用者がどちらにするか選ぶまで上書きしない。
    unknown は gBizINFO が空だった項目で、「なし」ではなく不明なので利用者に聞く。
    warnings は更新日が古い・代表者や従業員数の確認・業種が複数などの注意で、利用者に伝える。
    certifications(持っている認定)は前提の認定がある補助金の判定に使う。past_subsidies(過去の交付)は記録がないことを
    「交付を受けていない」と言わない。
    proposed・differences・unknown を利用者に見せ、確認を得てから get_company_profile の内容に足して save_company_profile で保存する。
    報告には attribution の出典の文言を必ず添える。法人番号がない個人事業主は対象外。
    

Input Schema

NameRequiredDescriptionDefault
nameNo
prefectureNo
corporate_numberNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations cover readOnlyHint and openWorldHint, and the description reinforces 'does not save' while adding far more: the meaning of proposed/differences/unknown/warnings, the rule not to overwrite existing values until the user chooses, the caution that missing past_subsidies records don't mean 'not received', and the mandatory attribution requirement.

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?

Purpose and the no-save guarantee are front-loaded, and the sentences are dense and information-bearing. It is long, but the length is mostly justified by the two-step workflow and output-field semantics; a little output-field detail could be trimmed given an output schema exists.

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?

For a complex read tool with 0% schema coverage and an output schema present, the description supplies the workflow, return-field semantics, scope limits, and attribution needs that the structured fields do not. Nothing essential to correct invocation 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 description coverage is 0%, so the description must carry parameter meaning, and it largely does: name returns a candidate list and can be narrowed by prefecture, and corporate_number is a 13-digit ID used after confirmation. prefecture gets only a brief mention, leaving a small gap.

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+resource: reads company info from gBizINFO (METI's corporate info site) by corporate number or company name. It explicitly distinguishes its two modes and separates itself from siblings like save_company_profile and get_company_profile. An agent can identify exactly what it does without opening the 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?

Gives an explicit workflow: use before asking the user about company info, call with name to get candidates, confirm the company with the user, then call with corporate_number. It names the downstream siblings (get_company_profile, save_company_profile) and states an exclusion (sole proprietors without a corporate number are out of scope).

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