One U Education

Get selected occupation topics

get_occupation

Read-onlyIdempotent

Multi-topic occupation query. sections is required: basic, visas, assessment, invitations, eoi, stateNomination, courses, labourAgreements. Loads only requested topics in parallel. EOI includes 189, 190 and 491; courses use the first 8 recommendations. For pagination or detailed topic filters use the standalone tools. Returns English prose for selected topics only, with identity, source links and explicit missing-data or failure explanations. Uses no business JSON or structured numeric copy. This public endpoint returns English natural-language text, preserving sources, conditions and pagination.

Input Schema

Name	Required	Description	Default
`locale`	No	Language 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
`sections`	Yes
`occupation`	Yes	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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 12, 2026

removedInput schema / properties / includeCourses

Removed value: -{
-  "default": false,
-  "description": "Also return up to 8 recommended courses leading to this occupation (one extra upstream call).",
-  "type": "boolean"
-}

removedInput schema / properties / includeSkillAssessment

Removed value: -{
-  "default": true,
-  "description": "Include the skills-assessment pathways (authority, processing times, requirements excerpt). Default true.",
-  "type": "boolean"
-}

changedInput schema / properties / occupation / description

Previous value: -"ANZSCO code such as \"254411\", or an occupation page URL / slug ending in the code."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."

addedInput schema / properties / occupation / maxLength
```
Added value: +300
```

addedInput schema / properties / sections

Added value: +{
+  "items": {
+    "enum": [
+      "basic",
+      "visas",
+      "assessment",
+      "invitations",
+      "eoi",
+      "stateNomination",
+      "courses",
+      "labourAgreements"
+    ],
+    "type": "string"
+  },
+  "maxItems": 8,
+  "minItems": 1,
+  "type": "array"
+}

changedInput schema / required

Previous value: -[
-  "occupation"
-]New value: +[
+  "occupation",
+  "sections"
+]

First observedOct 6, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent and open-world, so safety is covered. The description adds real behavioral context beyond that: topics load only as requested and in parallel, missing data/failures are surfaced explicitly, and output is prose rather than structured JSON.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the key facts (sections, parallel loading, EOI/courses scope), but the final three sentences repeat the same claim about English prose and preserved sources/conditions/pagination, which is redundant padding that could be cut to one sentence.

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 carries the return-value burden and does so: it specifies English prose, identity, source links, and explicit missing-data/failure signaling. It is nearly complete, but does not describe response size or how the multi-topic result is keyed.

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 67% and the schema already documents locale and occupation well. The description still adds meaning the schema cannot: that eoi spans visas 189/190/491 and courses return the first 8 recommendations, which clarifies what each section value actually yields.

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?

Opening phrase 'Multi-topic occupation query' states a specific verb+resource, and the sections list defines exactly what topics are retrievable. It partially differentiates from siblings by noting standalone tools exist for finer control, though it never names which sibling covers a single topic.

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?

It gives one clear routing rule — 'For pagination or detailed topic filters use the standalone tools' — which tells the agent when to leave this tool for a sibling. It stops short of stating the positive condition (use this when you want several topics at once), so guidance is present but not fully symmetric.

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 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?