Skip to main content
Glama
Sign In

Free Agent Tools

by io.github.akiba-labs
OverviewDiscussionsAdmin

When can I renew my visa / residence card in Japan? Window, last day, special period, fee

japan_visa_renewal_check
Read-onlyIdempotent

Applies ISA's renewal rules as of 2026-11-08 (在留期間更新許可申請 16-3, 特例期間, 在留カードの有効期間の更新申請, 特定在留カード Q&A, 2026-10-01 fee table). expiryDate required (period-of-stay expiry; for holder permanent / hsp2 the card's validity expiry). holder: fixed | permanent | hsp2. currentPeriodMonths (default 12; under 6 removes the 3-month rule), expectedGrantMonths (fee band), appliedDate (turns on the special period), birthDate (under-16 card rule, next card validity), cardIssueDate, method counter | online, wantSpecialCard, today. Returns verdict (too_early | open | urgent | pending | special_period | expired), summary, windowOpens, lastDay, daysLeft, specialPeriodEnd, fee {band, feeJPY, processingFeeJPY, totalJPY}, card16, nextCardValidity, processing, earlyExceptions, deadlines, actions, warnings, sources, disclaimer. Use for 'when can I renew my visa in Japan', '在留期間更新 いつから', '特例期間 いつまで', 'visa expired while renewal pending', '永住者 在留カード 更新 いつから', 'Japan visa renewal fee 2026'. Educational, not immigration or legal advice; not affiliated with ISA.

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

Input Schema

NameRequiredDescriptionDefault
todayNoAs-of date, YYYY-MM-DD (default today JST).
holderNofixed (any status with a period of stay, default) | permanent | hsp2.
methodNocounter (default) or online.
birthDateNoDate of birth, YYYY-MM-DD (optional).
expiryDateYesPeriod-of-stay expiry (or card expiry for permanent / hsp2), YYYY-MM-DD.
appliedDateNoDate you already applied, YYYY-MM-DD.
cardIssueDateNoResidence card issue date, YYYY-MM-DD (optional).
wantSpecialCardNoWants the 特定在留カード (card + My Number).
currentPeriodMonthsNoLength of the current period of stay in months (default 12).
expectedGrantMonthsNoPeriod you expect ISA to grant, for the fee (default = current).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the read-only and idempotent annotations, it identifies the ISA authorities and dates both the rules and fee table, which is essential context for time-sensitive immigration calculations. It also discloses its educational-only status and lack of ISA affiliation, notes that sources and warnings are returned, and explains behavioral triggers such as appliedDate activating the special period.

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

Conciseness3/5

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

The progression from legal basis to inputs, outputs, use cases, and disclaimer is logical and front-loaded with scope. However, the dense paragraph repeats schema enums and defaults, lists many output fields and source names, and includes six sample queries, making it less scannable than necessary.

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, date-sensitive tool with ten parameters and no output schema, it supplies the required-input clarification, holder scope, important rule triggers, verdict values, major return groups, legal effective dates, and limitations. This is sufficient for correct invocation and useful interpretation of the result, with sibling routing the main remaining omission.

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?

Although schema coverage is 100%, the description adds meaningful conditional behavior: a current period under six months removes the three-month rule, appliedDate enables the special period, and birthDate drives under-16 and next-card-validity logic. Other parameters, including cardIssueDate, wantSpecialCard, and today, are merely named or repeat information already present in the schema.

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 opening statement establishes that the tool applies ISA renewal rules, while the verdict, window, deadline, special-period, fee, and card outputs make its scope concrete for fixed, permanent, and hsp2 holders. It does not explicitly distinguish itself from siblings such as japan_visa_fee_check or japan_permanent_residency_check.

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 'Use for' examples provide clear invocation triggers, including renewal timing, the special-period deadline, expiration while an application is pending, permanent-resident card renewal, and 2026 fees. There is no when-not guidance or routing to an alternative for fee-only or permanent-residency-eligibility questions.

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

All Free Agent Tools 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