Skip to main content
Glama
Sign In
Edition Intelligence Platform

Edition Intelligence Platform

by hiroshic9-png
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

foreign_entry_check

Read-onlyIdempotent

Search for foundational knowledge required by foreign companies and individuals entering Japan, covering six categories: company incorporation, business manager visa, bank account opening, property search, tax filings, and employee hiring.

Instructions

外国企業・外国人の日本進出に必要な基盤知識を検索します。法人設立、経営管理ビザ、銀行口座開設、物件探し、税務届出、従業員雇用（労働法・解雇規制・社会保険）の6カテゴリ。

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

Input Schema

NameRequiredDescriptionDefault
queryYes検索クエリ（例: '法人設立の手順', 'ビザ取得', '銀行口座開設'）

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering safety. The description adds the specific categories of knowledge, which provides behavioral context but no further details like pagination or speed.

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 a single concise sentence that front-loads the purpose and lists categories. No extraneous information; efficient for the agent.

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

Completeness3/5

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

For a search tool with one parameter and no output schema, the description provides the search scope (categories) but does not hint at the output format (e.g., list of articles, summaries). This is a gap given the lack of output schema.

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 coverage is 100% and the query parameter description includes examples. The tool description does not add additional semantic meaning beyond the schema, so 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 clearly states it searches for foundational knowledge for foreign entry to Japan, listing 6 specific categories. This provides a clear scope and distinguishes it from sibling tools like foreign_entry_list, though explicit differentiation is absent.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like foreign_entry_list. The description only states what it does, leaving the agent to infer usage context.

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

Deploy Server

Other Tools