Skip to main content
Glama
Sign In

Free Agent Tools

by io.github.sean0007
OverviewDiscussionsAdmin

When can this dog, cat or rabbit fly into (or out of) Japan without quarantine detention, and what are the deadlines?

japan_pet_quarantine_check
Read-onlyIdempotent

Calculates Japan pet import / export / round-trip quarantine dates for dogs, cats and rabbits from the MAFF Animal Quarantine Service (AQS) rules, rules as of 2026-10-31. direction: import (bring a pet into Japan) | export (take it out of Japan) | return (leave Japan with the pet and come back: the short-stay route prepared before departure). species: dog | cat | rabbit. Non-designated regions (most countries incl. the US mainland, UK, EU, China, Korea): ISO 15-digit microchip first, then 2 rabies vaccinations (91+ days old, the 2nd after 30 days and within the 1st's validity), antibody blood test at a MAFF-designated lab (≥0.5 IU/ml, valid 2 years), then wait 180 days from the blood draw; arriving earlier means detention at the airport quarantine for the remaining days (up to 180). Designated regions (Iceland, Australia, New Zealand, Fiji, Hawaii, Guam): microchip + residence since birth or 180+ days (else detention for the difference). Always: notify AQS 40+ days before arrival, vet inspection and certificate within 10 days before boarding, ≤12h inspection on arrival when everything matches, register a dog with the city within 30 days. Short-stay return: prepare in Japan before leaving, return within the antibody's 2 years, no 180-day wait. Export: the 14-day-before application becomes MANDATORY for dogs and rabbits departing from 2027-01-01 (AQS asks for it for cats too). Returns verdict (on_track | plan | quarantine_risk | deadline_passed | redo_required), summary, steps [{step, date, status, rule}], dates {earliestArrival, antibodyValidUntil, notifyAqsBy, preDepartureInspectionFrom/To, exportApplyBy, registerDogBy}, exportApplication {mandatory}, quarantine {expected, days, reason}, fastestPlan (from today when nothing is done yet), actions, warnings (microchip format, vaccine gaps), ports (airports / seaports that accept dogs and cats), sources, disclaimer. Use for 'bring my dog to Japan', '犬 日本 輸入 180日', 'cat import Japan quarantine', 'Japan pet 40 days notice', 'ペット 輸出 14日前 義務化 2027', 'take my dog out of Japan and come back'. Educational date calculator, not veterinary or legal advice; not affiliated with MAFF / AQS; AQS and the destination country decide.

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": {
      "direction": "<direction>",
      "species": "<species>"
    },
    "name": "japan_pet_quarantine_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
titerNoAntibody result in IU/ml (pass ≥ 0.5).
todayNoOverride today's date (default: today in Japan).
originNoOverride: designated (Iceland, Australia, NZ, Fiji, Hawaii, Guam) | other.
countryNoimport: country / region the pet comes from (ISO code or name, e.g. US, GB, AU, Hawaii). Designated regions are detected automatically.
speciesYesdog | cat | rabbit.
birthDateNoPet's birth date YYYY-MM-DD (rabies shot 1 must be at 91+ days old).
directionYesimport = bring a pet into Japan | export = take it out of Japan | return = leave Japan with the pet and come back (short-stay route).
arrivalDateNoPlanned arrival in Japan YYYY-MM-DD (required for designated imports and once a blood draw is given).
vaccine1DateNo1st rabies vaccination (after the microchip).
vaccine2DateNo2nd rabies vaccination (30+ days after the 1st, within its validity).
bloodDrawDateNoAntibody (FAVN) blood draw date at a MAFF-designated lab; the 180 days count from this.
departureDateNoexport / return: departure from Japan YYYY-MM-DD.
microchipDateNoMicrochip implant date (must be on or before vaccine 1).
residentSinceNoDesignated region: date the pet started living there.
microchipNumberNoOptional chip number to check the ISO 15-digit format.
vaccineValidUntilNoValidity end of the latest vaccine (for booster warnings).
residentSinceBirthNoDesignated region: lived there since birth.
vaccine1ValidUntilNoValidity end of vaccine 1 (default 1 year).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes well past that: it enumerates the verdict values returned, the exact dates object fields, warnings, ports, sources and disclaimer, and pins the regulatory snapshot date. It also discloses that rules are time-sensitive (export 14-day application mandatory from 2027-01-01) and disclaims MAFF affiliation, which are traits no annotation conveys.

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?

Front-loaded with the core purpose and direction/species modes, then the rule detail, then the return shape — a sensible ordering. It is dense and repeats the direction and species enumerations already present in the schema, but nearly every clause carries regulatory substance for an 18-parameter tool with no output schema.

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?

With 18 parameters, no output schema, and a complex regulatory domain, the description compensates by enumerating the return fields, the verdict set, and the non-designated vs designated region rule branches. An agent has enough to decide whether to call it and how to interpret the result without further documentation.

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 parameters are already documented, but the description adds real interpretive value by laying out the rule chain (microchip → vaccine 1 → vaccine 2 → blood draw → 180-day wait) that explains why each date parameter matters and how they interact. It does not add syntax or format detail beyond the schema, so it stops short of a 5.

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 ('Calculates Japan pet import / export / round-trip quarantine dates') plus the covered species and rule source (MAFF AQS, rules as of 2026-10-31). No sibling tool covers pet quarantine, and the description makes that domain boundary immediately obvious.

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?

Defines each direction mode (import / export / return) with plain-language glosses and supplies concrete trigger phrases in both English and Japanese, so an agent can route a user request to the right mode. It also flags scope limits ('educational date calculator, not veterinary or legal advice; AQS and the destination country decide') but gives no explicit when-not-to-use-this-tool alternative.

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