One U Education

Discover planning occupations and source coverage

search_planning_occupations

Read-onlyIdempotent

Discover the complete Forms occupation catalogue with an optional keyword and coarse category from get_planning_input_options. Empty q explicitly discovers a page. Reuse next_cursor unchanged with the same query; source/query changes fail visibly. Keeps distinct internal identities sharing an ANZSCO classification. Source coverage present/absent/unavailable is not personal eligibility, predictability, a recommendation score or an invitation date. No dossier, saving, quota debit or calculation. Use existing occupation topic tools for duties, assessment and courses; only explicit user selection within save authorization may update goals. Requires the authenticated One U Education account and declared planning scope; credentials and user identity are never tool arguments.

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": "search_planning_occupations"
  }
}

Input Schema

Name	Required	Description	Default
`q`	No
`limit`	No
`cursor`	No
`category`	No

Output Schema

Name	Required	Description	Default
`msg`	Yes
`code`	Yes
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 1, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already mark this read-only, idempotent, and non-destructive, yet the description still adds substantive behavior: query/source changes fail visibly, distinct internal identities sharing one ANZSCO are kept, and coverage states are explicitly not eligibility, predictability, scores, or invitation dates. It also discloses the auth/planning-scope prerequisite and that no dossier, saving, quota debit, or calculation occurs, which the annotations cannot express.

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?

Front-loaded with purpose and the discovery/cursor rules, and nearly every clause carries distinct information (identity handling, coverage disclaimers, auth). It is dense and runs long as a single block; the negative-capability list could be tightened without losing meaning.

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?

An output schema exists, so return values need not be explained, and the description covers what remains: auth and planning-scope requirements, pagination discipline, identity/classification behavior, and explicit non-capabilities. Nothing an agent needs to call this correctly appears to be missing, aside from the minor limit gap.

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?

With 0% schema description coverage, the description must carry the load and mostly does: it defines empty-q semantics, the cursor reuse contract, and that category is a coarse value sourced from get_planning_input_options. The limit parameter is never explained, leaving one of four parameters without meaning in either field.

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?

States a specific verb and resource ('Discover the complete Forms occupation catalogue') plus the two filter axes (keyword, coarse category). It implicitly separates itself from topic-level tools ('Use existing occupation topic tools for duties, assessment and courses') but never names the closest sibling, search_occupations, so the boundary with that tool is left to inference.

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?

Gives real selection conditions: empty q explicitly means 'discover a page', cursor must be reused unchanged with the same query, and duties/assessment/courses belong to other topic tools. It stops short of naming which sibling to pick for overlapping occupation lookups, and the save-authorization clause is stated as a constraint rather than a routing rule.

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?