Tern Australian Visa Information

Working holiday specified work (88 days) postcode check

check_88_day_area

Read-onlyIdempotent

Whether work in an industry at an Australian postcode is on the Department of Home Affairs' specified work lists for a second or third working holiday visa (the 88 or 179 days), for subclass 417 or 462. Checks every industry unless one is given.

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": {
      "postcode": "<postcode>",
      "subclass": "<subclass>"
    },
    "name": "check_88_day_area"
  }
}

Input Schema

Name	Required	Description
`industry`	No	One industry to check: plantAnimalCultivation, tourismHospitality, construction, fishingPearling, treeFarmingFelling, mining, bushfireRecovery, disasterRecovery. Omit to check all.
`postcode`	Yes	Four-digit Australian postcode.
`subclass`	Yes	The working holiday subclass the person holds.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the agent knows this is a safe, deterministic lookup. The description adds the authoritative source (Department of Home Affairs lists) and the all-industries default, but says nothing about how results are shaped when multiple industries are checked, or whether list data may lag policy changes.

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?

Two dense sentences with no filler; the core predicate comes first and the default-scope caveat follows. The opening clause is slightly convoluted ('Whether work in an industry at an Australian postcode is on...'), but the parenthetical 88/179-day gloss resolves the domain jargon efficiently.

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 three-parameter lookup with no output schema, the description should hint at the return shape — a single boolean versus per-industry results when no industry is specified. It implies a yes/no answer but leaves multi-industry output ambiguous, which is the main completeness gap.

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 description coverage is 100% and both enums are self-documenting, so the schema carries the parameter burden. The description only restates the industry-omission behavior already present in the schema and adds no format or edge-case detail beyond it — baseline 3 applies.

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?

The description names a specific predicate — whether work in a given industry at an Australian postcode appears on the Department of Home Affairs' specified work lists — and scopes it to subclass 417/462 and the 88/179-day schemes. This is unmistakably distinct from siblings like get_whm_cap_status or get_visa_fees, which concern different resources.

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

Usage Guidelines3/5

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

The final sentence gives one useful scoping cue: 'Checks every industry unless one is given,' which tells the agent the default behavior when industry is omitted. However, there is no explicit guidance on when to reach for this tool versus related visa tools, and no stated exclusions or preconditions.

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

All Tern Australian Visa Information tools Inspect

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

Need Help?