A
licenseNot graded
qualityD
maintenanceExposes a public, read-only professional profile with tools to search resume evidence, fetch curated links, and generate career briefs for LLM agents.
MIT
Rung public career guides
by guru.rung
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 with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
TDQS
A4.2/5.0
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 toolsexplore_occupationExplore public occupation examplesARead-onlyIdempotentInspect
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 guideARead-onlyIdempotentInspect
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. Dates show when Glama detected each change.
2 tool updates
- Changed
explore_occupation10 fields changed- added
Output schema / additionalPropertiesAdded value: +false - added
Output schema / properties / contentLanguage / enumAdded value: +[ + "en", + "es", + "ko", + "zh" +] - added
Output schema / properties / occupation / additionalPropertiesAdded value: +false - added
Output schema / properties / occupation / propertiesAdded value: +{ + "description": { + "type": "string" + }, + "name": { + "type": "string" + }, + "officialName": { + "type": "string" + }, + "soc": { + "pattern": "^\\d{2}-\\d{4}\\.\\d{2}$", + "type": "string" + } +} - added
Output schema / properties / occupation / requiredAdded value: +[ + "name", + "officialName", + "soc", + "description" +] - added
Output schema / properties / requestedLanguage / enumAdded value: +[ + "en", + "es", + "ko", + "zh" +] - added
Output schema / properties / requestedSection / enumAdded value: +[ + "all", + "tasks", + "skills", + "tools" +] - added
Output schema / properties / sections / additionalPropertiesAdded value: +false - added
Output schema / properties / sections / minPropertiesAdded value: +1 - added
Output schema / properties / sections / propertiesAdded 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" + } +}
- Changed
find_public_guides6 fields changed- added
Input schema / properties / query / x-rung-trimmedMinLengthAdded value: +2 - added
Output schema / additionalPropertiesAdded value: +false - added
Output schema / properties / kind / enumAdded value: +[ + "all", + "occupation", + "situation", + "military" +] - added
Output schema / properties / requestedLanguage / enumAdded value: +[ + "en", + "es", + "ko", + "zh" +] - added
Output schema / properties / results / items / oneOfAdded 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" + } +] - removed
Output schema / properties / results / items / typeRemoved value: -"object"
2 tool updates
- First observed
explore_occupation - First observed
find_public_guides
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
- ResuMaxOAuthai.resumax
Find jobs, improve resumes, prepare for interviews, and manage your application pipeline.
Career assistant: resumes, job-match analysis, interview results and career memory.
Discover US remote roles, match your experience, and create tailored resumes and cover letters.
Related MCP Servers
- AlicenseAqualityCmaintenanceProvides job search, local resume parsing, and resume-to-job matching via official APIs and local file processing.5MIT
- AlicenseCqualityAmaintenanceEnables 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.4MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to search and analyze job listings from verified company boards privately, matching resumes to roles with evidence and suggesting resume improvements.MIT