Skip to main content
Glama

One U Education

by com.oneuedu.mcp
OverviewDiscussionsAdmin

Get state nomination (190 / 491) programs

get_state_nomination
Read-onlyIdempotent

State policy overview and exact program directory for subclass 190/491, with nomination places (allocation, used, remaining). Add occupation for program list matches and invitation records. program only filters briefs. Full policy is in get_state_nomination_detail; lists are in get_state_nomination_occupations. This public endpoint returns English natural-language text, preserving sources, conditions and pagination.

Input Schema

NameRequiredDescriptionDefault
stateNoState or territory: ACT, NSW, NT, QLD, SA, TAS, VIC or WA. Omit for an all-states overview.
localeNoLanguage of names/descriptions in the result: zh-CN (default, Simplified Chinese plus English names), en-US, zh-TW. Also selects the language prefix of returned oneuedu.com URLs.zh-CN
programNoExact program name from a previous result (e.g. "TAS subclass 190 - Tasmanian Skilled Graduate (TSG)") to filter the brief program directory; use get_state_nomination_detail with programRules for full rules.
occupationNoInternal occupationCode from search_occupations, or occupation URL/slug. anzsco is a shared classification code, not a unique identity. Exact internal code matches take precedence; search to select a candidate only if no exact match exists.
visaSubclassNoOnly programs for subclass 190 (Skilled Nominated) or 491 (Skilled Work Regional).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / properties / includeOccupationList
      Removed value: -{
-  "default": false,
-  "description": "With state (and ideally visaSubclass or program): also list the occupations each program accepts, 40 per page.",
-  "type": "boolean"
-}
    • changedInput schema / properties / occupation / description
      Previous value: -"ANZSCO code (or occupation URL / slug). Adds whether each program accepts this occupation and the state invitation records that match it."New value: +"Internal occupationCode from search_occupations, or occupation URL/slug. anzsco is a shared classification code, not a unique identity. Exact internal code matches take precedence; search to select a candidate only if no exact match exists."
    • removedInput schema / properties / page
      Removed value: -{
-  "default": 1,
-  "description": "Page of the occupation list (includeOccupationList).",
-  "minimum": 1,
-  "type": "integer"
-}
    • changedInput schema / properties / program / description
      Previous value: -"Exact program name from a previous result (e.g. \"TAS subclass 190 - Tasmanian Skilled Graduate (TSG)\") for that program in full detail."New value: +"Exact program name from a previous result (e.g. \"TAS subclass 190 - Tasmanian Skilled Graduate (TSG)\") to filter the brief program directory; use get_state_nomination_detail with programRules for full rules."
  2. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the bar is lower; the description still adds real context: this is a public endpoint (no auth), returns English natural-language text, and preserves sources, conditions and pagination. It stops short of rate limits or error behavior, so it is strong but not exhaustive.

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?

Content is front-loaded (what it returns first, sibling routing next, endpoint behavior last) and short. A few telegraphic fragments ('program only filters briefs') are dense but not wasteful.

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?

With no output schema, the description must carry return-value burden; it does so by naming the returned units (allocation, used, remaining) and the response format (natural-language text with sources/pagination). For a 5-parameter, all-optional tool this is largely sufficient, though the shape of the program directory entries is only loosely characterized.

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 the baseline is 3, but the description adds meaning beyond the schema: occupation is what triggers program-list matches and invitation records, and program 'only filters briefs' rather than full rules. These behavioral effects are not visible in the parameter descriptions themselves.

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 states a specific resource and scope: state policy overview plus exact 190/491 program directory including nomination places (allocation, used, remaining). It also names the two closest siblings (get_state_nomination_detail, get_state_nomination_occupations) and how they differ, so an agent can distinguish it without opening schemas.

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

Usage Guidelines5/5

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

It explicitly routes to alternatives with conditions: 'Full policy is in get_state_nomination_detail; lists are in get_state_nomination_occupations,' and adds a caveat that 'program only filters briefs.' The boundary between this tool and its nearest siblings is stated, not inferred.

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

All One U Education 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