Tern Australian Visa Information

Work and Holiday (462) country cap status

get_whm_cap_status

Read-onlyIdempotent

Whether each Work and Holiday visa (subclass 462) country cap is open, paused, closed or allocated by ballot, when that was last checked, and the recent openings Tern has detected. Subclass 417 countries have no per-country cap.

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_whm_cap_status"
  }
}

Input Schema

Name	Required	Description	Default
`country`	No	Two-letter passport country code, e.g. "ES". Omit for every capped country.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare this as a read-only, idempotent, non-destructive, closed-world operation, so the safety profile is covered. The description adds useful content context by naming the returned status categories and the last-checked timestamp. It does not add behavioral details like data freshness caveats or update frequency beyond what the timestamp field implies.

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?

Two sentences with no wasted wording. The core purpose and returned fields are front-loaded, and the 417 scope exclusion follows efficiently.

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 simple read-only status tool with one optional parameter, complete annotations, and no output schema, the description covers what is returned and the important 417 scope boundary. Nothing an agent needs in order to call it correctly 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 description coverage is 100%, and the schema fully documents the single optional country parameter, including the two-letter pattern and the omit-for-all behavior. The description does not add any parameter meaning beyond that. Baseline 3 is appropriate.

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 states exactly what the tool returns: per-country Work and Holiday (462) cap status, possible status values, last-checked time, and recent openings. It also clarifies that 417 countries have no per-country cap, which prevents a likely scope error. It does not explicitly distinguish itself from sibling tools like get_country_profile, so it falls short of a 5.

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?

Usage is implied by the specific subject matter: check 462 cap status. The only explicit exclusion is that 417 countries have no per-country cap, which is useful. There is no explicit when-to-use guidance or named alternative for related policy or country queries.

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?