Skip to main content
Glama
Sign In

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

by io.github.takaratomita
OverviewDiscussionsAdmin

Search Japanese registered support organizations (SSW)

search_support_orgs
Read-onlyIdempotent

Search the Immigration Services Agency of Japan registry of Registered Support Organizations for Specified Skilled Workers. Filter by name, location (prefecture/city in head office or support office address) and supported language. Organizations that reported suspension are excluded unless includeSuspended is true. 出入国在留管理庁「登録支援機関登録簿」から、特定技能外国人の登録支援機関を名称・所在地・対応言語で検索します（同梱データ・基準日あり）。

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": "search_support_orgs"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoOrganization name, partial match / 名称（部分一致）
limitNoMax results (default 10, max 20) / 最大件数
languageNoSupported language in Japanese / 対応言語（例：ベトナム語、英語）
locationNoPrefecture or city, partial match on address / 所在地（例：東京都、横浜市。住所の部分一致）
includeSuspendedNoInclude organizations that reported suspension / 支援業務休止の届出がある機関も含める

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive behaviour, so the safety profile is covered. The description adds genuinely new context: suspended organizations are excluded by default unless includeSuspended is true, and location matching covers both head-office and support-office addresses. It does not explain pagination or result-shape limits beyond what the schema states.

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 key scoping facts appear first, and each sentence carries information the agent needs (registry identity, filter dimensions, suspension default). The bilingual restatement of the same content doubles the length without adding information, but it may serve mixed-language agents and the text remains short.

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 no output schema and fully documented parameters, the description covers what an agent needs to call it correctly: what is searched, what can be filtered, and the default exclusion rule. It does not describe the returned record fields or any rate-limit behaviour, which are minor gaps for a read-only lookup limited to 20 results.

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 the baseline is 3. The description still adds meaning beyond the schema: it says location matches both head-office and support-office addresses, and it clarifies the default meaning of includeSuspended (that suspended organizations are excluded unless the flag is set). This is more than the schema's bare field descriptions provide.

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 (search) and a precisely named resource (Immigration Services Agency of Japan registry of Registered Support Organizations for Specified Skilled Workers). This is clearly distinguishable from the sibling tools about corporate numbers and local government bids, so no sibling differentiation is needed.

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 a clear context for use: an official registry lookup, filterable by name, location and language. It states the default behaviour (exclusion of suspended organizations) but does not explain when to use this instead of other tools or what the constraints are beyond that. The siblings are unrelated, so the cost of this omission is small.

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

All Japan Public Data (法人番号・登録支援機関・官公需入札) toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources