Tern Australian Visa Information

Australian government visa charges

get_visa_fees

Read-onlyIdempotent

The Department of Home Affairs' current visa application charges for an Australian visa subclass, per stream: main applicant, each additional adult and child, and any lower charges for particular passports. Amounts in AUD. These are government charges, not Tern's fees.

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

Input Schema

Name	Required	Description	Default
`subclass`	Yes	Visa subclass, e.g. "820" or "600".

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4/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 bar is lower. The description still adds real context beyond that: amounts are in AUD, they are current (point-in-time) government charges rather than Tern's margin, charges vary by stream and by passport held. It does not say what happens for an unknown or invalid subclass, which is the main remaining gap.

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 short, front-loaded sentences with no filler: resource first, breakdown second, currency and fee-ownership qualifier last. Every sentence contributes information an agent would act on.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter lookup with no output schema, the description does the necessary work by describing the shape of the returned figures (per stream, per applicant type, AUD). Only the error/unknown-subclass behavior is left unstated, which is a minor omission at this complexity.

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?

There is a single parameter with 100% schema coverage including a pattern and example, so the schema carries the load. The description adds meaning about why the subclass matters (it drives per-stream and passport-dependent amounts) but does not explain the apparent hidden dependency on passport nationality, which has no corresponding input parameter.

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 resource (Department of Home Affairs visa application charges) and scope (per Australian visa subclass, broken down by stream: main applicant, additional adult, child, passport-based reductions). The closing clause 'not Tern's fees' explicitly separates it from the sibling get_tern_services, so an agent can route without opening either schema.

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 rather than stated: 'These are government charges, not Tern's fees' tells the agent this is not the right tool for Tern pricing, but it never names an alternative or says when to prefer one tool over another. There is no explicit exclusion or prerequisite guidance.

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?