Rung public career guides

Server Details

Find public career guides, explore grounded occupations, and open Rung for private resume work.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.

Status: Healthy
Uptime: 100.0% over 42 days
Last Tested: 2026-09-28 17:43
Transport: Streamable HTTP · MCP 2025-11-25
URL

TDQS

A4.2/5.0

Scored 2026-08-19 07:40 across 2 tools

Disambiguation4/5

The two tools have distinct purposes: find_public_guides locates guides, while explore_occupation provides detailed occupation examples. There is a slight dependency (explore_occupation is meant to be used after find_public_guides), but the descriptions clearly delineate their roles, minimizing confusion.

Naming Consistency4/5

Both tool names follow a verb_noun pattern (find_public_guides, explore_occupation), which is consistent. The verbs 'find' and 'explore' are slightly different in style but both are clear and appropriate for their functions.

Tool Count3/5

With only two tools, the server is minimal but not trivial. The tools cover a specific workflow (find then explore), which is reasonable for a narrow purpose, but the count is on the low end of the acceptable range.

Completeness3/5

The tool surface covers the core workflow of finding and exploring public guides, but there are potential gaps such as listing all available guides or retrieving specific guide details without exploration. The domain is narrow, so the coverage is adequate but not comprehensive.

Available Tools

2 tools

explore_occupationExplore public occupation examplesA

Read-onlyIdempotent

Inspect

Use after find_public_guides resolves an exact published Rung SOC, when bounded public task, skill, or tool examples are needed. Do not treat examples as a person's experience, selected skills, qualifications, or any other personal claim; never send personal or resume data.

ParametersJSON Schema

Name	Required	Description	Default
`soc`	Yes	The exact published occupation code returned by find_public_guides.
`limit`	No
`offset`	No
`section`	No		all
`language`	No		en

Output Schema

ParametersJSON Schema

Name	Required	Description
`caution`	Yes
`privacy`	Yes
`guideUrl`	Yes
`sections`	Yes
`startUrl`	Yes
`occupation`	Yes
`contentLanguage`	Yes
`requestedSection`	Yes
`requestedLanguage`	Yes

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already indicate read-only and idempotent behavior, and the description reinforces this by emphasizing public data and warning against personal use. It adds context about the nature of the data without contradicting the annotations.

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?

The description is concise, consisting of two sentences that deliver all key information without redundancy. It is well-structured and front-loaded with the primary usage scenario.

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?

The description provides enough context for when and how to use the tool, including misuse warnings. Since an output schema exists, the description does not need to elaborate on return format. It could mention that it returns example data, but the phrase 'examples are needed' implies this.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only the 'soc' parameter has a description in the schema (20% coverage). The tool description does not explain the roles of limit, offset, section, or language, leaving their semantics unclear. It does add indirect context for 'soc' by linking it to an exact Rung, but overall parameter guidance is insufficient.

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 clearly states the tool's purpose: to explore public occupation examples after finding an exact Rung via find_public_guides. It distinguishes itself from the sibling tool by focusing on bounded examples rather than general guides.

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 provides explicit usage context: use after find_public_guides, when bounded examples are needed. It also gives clear prohibitions (not treating examples as personal claims, not sending personal data), which are valuable guidelines.

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

find_public_guidesFind a published Rung guideA

Read-onlyIdempotent

Inspect

Use when someone needs a published Rung occupation, resume-situation, or military-transition guide. Returns public guide facts, source pages, and browser handoffs. Do not use for live jobs, employer search, resume editing, qualification decisions, or private work history; never send personal or resume data.

ParametersJSON Schema

Name	Required	Description	Default
`kind`	No		all
`limit`	No
`query`	Yes	A public job title, occupation code, situation, military code, or military role.
`language`	No	Language for occupation and situation guides. Military guides are currently English.	en

Output Schema

ParametersJSON Schema

Name	Required	Description
`kind`	Yes
`query`	Yes
`privacy`	Yes
`results`	Yes
`requestedLanguage`	Yes

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is largely covered. The description adds value by clarifying that only public data is returned, that browser handoffs/source pages may be produced, and that personal/resume data should never be sent—useful behavioral context beyond the annotations.

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?

The description is two concise, front-loaded sentences: the first explains when to use it, the second explains what it returns and what it must not be used for. Every sentence carries key decision information with no wasted words.

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?

Given that annotations cover safety/idempotency, the schema documents all parameters, and an output schema is present, the description supplies the remaining elements: purpose, usage boundary, return types, and critical privacy guardrail. The tool is adequately described for an agent to select and invoke it.

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?

The description maps directly onto the 'kind' parameter categories ('occupation, resume-situation, military-transition'), while 'query' and 'language' are already documented in the schema. The limit parameter is adequately self-evident through its default, minimum, and maximum constraints.

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 clearly states the tool's verb and resource: it finds a published Rung occupation, resume-situation, or military-transition guide. It also names the return content ('public guide facts, source pages, and browser handoffs') and separates this from other search/editing tasks, making its purpose distinct.

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?

The description starts with an explicit 'Use when someone needs...' trigger and then gives concrete exclusions: 'Do not use for live jobs, employer search, resume editing, qualification decisions, or private work history; never send personal or resume data.' This gives the agent actionable choose/avoid guidance.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

2 tool updatesAug 19, 2026

Changedexplore_occupation10 fields changed

addedOutput schema / additionalProperties
```
Added value: +false
```

addedOutput schema / properties / contentLanguage / enum

Added value: +[
+  "en",
+  "es",
+  "ko",
+  "zh"
+]

addedOutput schema / properties / occupation / additionalProperties
```
Added value: +false
```

addedOutput schema / properties / occupation / properties

Added value: +{
+  "description": {
+    "type": "string"
+  },
+  "name": {
+    "type": "string"
+  },
+  "officialName": {
+    "type": "string"
+  },
+  "soc": {
+    "pattern": "^\\d{2}-\\d{4}\\.\\d{2}$",
+    "type": "string"
+  }
+}

addedOutput schema / properties / occupation / required

Added value: +[
+  "name",
+  "officialName",
+  "soc",
+  "description"
+]

addedOutput schema / properties / requestedLanguage / enum
```
Added value: +[
+  "en",
+  "es",
+  "ko",
+  "zh"
+]
```

addedOutput schema / properties / requestedSection / enum

Added value: +[
+  "all",
+  "tasks",
+  "skills",
+  "tools"
+]

addedOutput schema / properties / sections / additionalProperties
```
Added value: +false
```
addedOutput schema / properties / sections / minProperties
```
Added value: +1
```

addedOutput schema / properties / sections / properties

Added value: +{
+  "skills": {
+    "additionalProperties": false,
+    "properties": {
+      "hasMore": {
+        "type": "boolean"
+      },
+      "items": {
+        "items": {
+          "type": "string"
+        },
+        "maxItems": 12,
+        "type": "array"
+      },
+      "language": {
+        "enum": [
+          "en",
+          "es",
+          "ko",
+          "zh"
+        ],
+        "type": "string"
+      },
+      "offset": {
+        "maximum": 100,
+        "minimum": 0,
+        "type": "integer"
+      },
+      "returned": {
+        "maximum": 12,
+        "minimum": 0,
+        "type": "integer"
+      },
+      "total": {
+        "minimum": 0,
+        "type": "integer"
+      }
+    },
+    "required": [
+      "language",
+      "total",
+      "offset",
+      "returned",
+      "items",
+      "hasMore"
+    ],
+    "type": "object"
+  },
+  "tasks": {
+    "additionalProperties": false,
+    "properties": {
+      "hasMore": {
+        "type": "boolean"
+      },
+      "items": {
+        "items": {
+          "type": "string"
+        },
+        "maxItems": 12,
+        "type": "array"
+      },
+      "language": {
+        "enum": [
+          "en",
+          "es",
+          "ko",
+          "zh"
+        ],
+        "type": "string"
+      },
+      "offset": {
+        "maximum": 100,
+        "minimum": 0,
+        "type": "integer"
+      },
+      "returned": {
+        "maximum": 12,
+        "minimum": 0,
+        "type": "integer"
+      },
+      "total": {
+        "minimum": 0,
+        "type": "integer"
+      }
+    },
+    "required": [
+      "language",
+      "total",
+      "offset",
+      "returned",
+      "items",
+      "hasMore"
+    ],
+    "type": "object"
+  },
+  "tools": {
+    "additionalProperties": false,
+    "properties": {
+      "hasMore": {
+        "type": "boolean"
+      },
+      "items": {
+        "items": {
+          "type": "string"
+        },
+        "maxItems": 12,
+        "type": "array"
+      },
+      "language": {
+        "enum": [
+          "en",
+          "es",
+          "ko",
+          "zh"
+        ],
+        "type": "string"
+      },
+      "offset": {
+        "maximum": 100,
+        "minimum": 0,
+        "type": "integer"
+      },
+      "returned": {
+        "maximum": 12,
+        "minimum": 0,
+        "type": "integer"
+      },
+      "total": {
+        "minimum": 0,
+        "type": "integer"
+      }
+    },
+    "required": [
+      "language",
+      "total",
+      "offset",
+      "returned",
+      "items",
+      "hasMore"
+    ],
+    "type": "object"
+  }
+}

Changedfind_public_guides6 fields changed

addedInput schema / properties / query / x-rung-trimmedMinLength
```
Added value: +2
```
addedOutput schema / additionalProperties
```
Added value: +false
```

addedOutput schema / properties / kind / enum

Added value: +[
+  "all",
+  "occupation",
+  "situation",
+  "military"
+]

addedOutput schema / properties / requestedLanguage / enum
```
Added value: +[
+  "en",
+  "es",
+  "ko",
+  "zh"
+]
```

addedOutput schema / properties / results / items / oneOf

Added value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "description": {
+        "type": "string"
+      },
+      "guideUrl": {
+        "type": "string"
+      },
+      "kind": {
+        "const": "occupation"
+      },
+      "language": {
+        "enum": [
+          "en",
+          "es",
+          "ko",
+          "zh"
+        ],
+        "type": "string"
+      },
+      "matchScore": {
+        "maximum": 100,
+        "minimum": 0,
+        "type": "integer"
+      },
+      "name": {
+        "type": "string"
+      },
+      "officialName": {
+        "type": "string"
+      },
+      "soc": {
+        "pattern": "^\\d{2}-\\d{4}\\.\\d{2}$",
+        "type": "string"
+      },
+      "startUrl": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "kind",
+      "language",
+      "name",
+      "officialName",
+      "soc",
+      "description",
+      "guideUrl",
+      "startUrl",
+      "matchScore"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "description": {
+        "type": "string"
+      },
+      "guideUrl": {
+        "type": "string"
+      },
+      "kind": {
+        "const": "situation"
+      },
+      "language": {
+        "enum": [
+          "en",
+          "es",
+          "ko",
+          "zh"
+        ],
+        "type": "string"
+      },
+      "matchScore": {
+        "maximum": 100,
+        "minimum": 0,
+        "type": "integer"
+      },
+      "name": {
+        "type": "string"
+      },
+      "startUrl": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "kind",
+      "language",
+      "name",
+      "description",
+      "guideUrl",
+      "startUrl",
+      "matchScore"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "branch": {
+        "type": "string"
+      },
+      "caution": {
+        "type": "string"
+      },
+      "civilianDirections": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "guideUrl": {
+              "type": "string"
+            },
+            "name": {
+              "type": "string"
+            },
+            "soc": {
+              "type": "string"
+            },
+            "startUrl": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "soc",
+            "name",
+            "guideUrl",
+            "startUrl"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "code": {
+        "type": "string"
+      },
+      "guideUrl": {
+        "type": "string"
+      },
+      "kind": {
+        "const": "military"
+      },
+      "language": {
+        "enum": [
+          "en",
+          "es",
+          "ko",
+          "zh"
+        ],
+        "type": "string"
+      },
+      "matchScore": {
+        "maximum": 100,
+        "minimum": 0,
+        "type": "integer"
+      },
+      "name": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "kind",
+      "language",
+      "name",
+      "branch",
+      "code",
+      "guideUrl",
+      "civilianDirections",
+      "caution",
+      "matchScore"
+    ],
+    "type": "object"
+  }
+]

removedOutput schema / properties / results / items / type
```
Removed value: -"object"
```

2 tool updatesAug 18, 2026
- First observedexplore_occupation
- First observedfind_public_guides

Related MCP Connectors

ResuMaxOAuth
ai.resumax
Find jobs, improve resumes, prepare for interviews, and manage your application pipeline.
Search Education & Learning Tools Workplace & Productivity
1
mcp
ai.skillsinput
AI-powered career tools: job search, skills intelligence, career roadmaps, and resume building.
Education & Learning Tools Search
1
ResumeQuick
app.resumequick
Career assistant: resumes, job-match analysis, interview results and career memory.
Knowledge & Memory AI & Machine Learning Search
2
ApplyAll A
com.applyall
Search for jobs and apply to jobs.
Search App Automation
201

Related MCP Servers

mundigital
Search
mundizzle
A
license
Not graded
quality
D
maintenance
Exposes a public, read-only professional profile with tools to search resume evidence, fetch curated links, and generate career briefs for LLM agents.
Updated 3 days ago (2026-09-25 17:17 UTC)
MIT
JobLens MCP
Search Research & Data
rohith-jpg
A
license
A
quality
C
maintenance
Provides job search, local resume parsing, and resume-to-job matching via official APIs and local file processing.
Updated 2 months ago (2026-07-21 05:08 UTC)
5
MIT
Career Agent Workbench MCP
Search
mperkhou
A
license
C
quality
A
maintenance
Enables natural-language access to workspace-independent public job search, matching, and seeding tools, along with lazy job matching, while keeping private data and application state in a separate operator-owned workspace.
Updated 2 months ago (2026-08-05 17:20 UTC)
4
MIT
openings
Search
abhay-avagama
A
license
Not graded
quality
A
maintenance
Enables AI agents to search and analyze job listings from verified company boards privately, matching resumes to roles with evidence and suggesting resume improvements.
Updated 6 days ago (2026-09-22 14:58 UTC)
472 npm
MIT

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?

Server Details

TDQS

Available Tools

Output Schema

TDQS

Output Schema

TDQS

Tool Schema Changelog

Related MCP Connectors

Related MCP Servers

mundigital

JobLens MCP

Career Agent Workbench MCP

openings

Glama MCP Gateway

Resources