Skip to main content
Glama

DinCat — learning and life in Japan

Japan visa and residence rules (DinCat summary)

get_visa_rules
Read-onlyIdempotent

Get DinCat's summary of Japan's residence-status (visa) rules for one or more topics, compiled from official Immigration Services Agency pages, with the official sources. Information and self-check points only: it does not judge whether an application will be approved, and does not write or fill in application documents. Call without topics to list the topics.

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

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the reply and of the linked pages: ja = Japanese, zh = Simplified Chinese, en = English. Use the user's language.ja
topicsNoUp to 4 topics: renewal = Extension of period of stay / change of status; fees = Fees (applications accepted from 2026-10-01); pr = Permanent residence; naturalization = Naturalization (Japanese nationality); job_change = Notifications after changing or leaving a job; student_work = From student to work; family_stay = Family / Dependent status; dependent = Dependent procedures (bringing family over, renewal); spouse_jp = Spouse of a Japanese national (status: Spouse or Child of Japanese National); spouse_pr = Spouse of a permanent resident (status: Spouse or Child of Permanent Resident); hire = First work visa for a foreign hire (company / HR); employer = Company / HR side (employing foreign staff); school = Japanese language school side (international students); short_stay = Temporary visitor (tourism, business trips, visiting family); referral = Cases to refer to professionals; dv = Domestic violence and visas. Omit to list the topics.

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, non-destructive and closed-world, so the safety profile is covered. The description adds context the annotations cannot: the content is a compiled summary with citations to official sources, it is explicitly informational with self-check points, and it does not assess approval odds or generate documents. Minor gap: nothing about response size or how topics are presented.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with purpose and provenance, then boundaries, then the zero-argument discovery instruction. Every clause carries information; nothing is padding.

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 read-only, two-parameter, no-output-schema tool, the definition covers what the tool returns (summaries plus official sources), its limits, and how to call it with zero arguments. Annotations handle the rest of the safety semantics, so nothing an agent needs is missing.

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 topics enum already enumerates and defines all 16 topic values, including 'Omit to list the topics'. The description only restates the topic-list discovery behavior, which also appears in the schema, so it adds little meaning beyond the structured fields.

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 and resource — 'Get DinCat's summary of Japan's residence-status (visa) rules' — plus scope ('one or more topics') and provenance ('compiled from official Immigration Services Agency pages, with the official sources'). No sibling overlaps this domain (service info, take-home pay, library), so no disambiguation is needed for an agent to select it.

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?

Gives explicit invocation guidance — 'Call without topics to list the topics' — which tells the agent how to bootstrap topic discovery. It also carves out when the tool is not appropriate ('does not judge whether an application will be approved, and does not write or fill in application documents'), though it does not name an alternative for those cases.

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