Skip to main content
Glama

Get an occupation's PERM record

get_occupation
Read-onlyIdempotent

One occupation's PERM record, with its SOC code and median offered wage, and its cases pending at DOL now. Find the slug with the search first. Example: {"slug":"software-developers"}.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "get_occupation"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe name in its page's address, as search returns it. Example: software-developers.

Output Schema

NameRequiredDescriptionDefault
asOfYesThe date the data is true for, YYYY-MM-DD, when one applies.
dataYesThe answer, or found: false when no record matched.
pageYesThe page on permtracker.app that shows the same thing. Cite it.
sourceYesWho published the underlying records.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds useful context: the record includes live 'cases pending at DOL now', signaling currently-refreshing data rather than a static snapshot. It does not discuss rate limits or what happens for an unknown slug, but with full annotation coverage that is a minor gap.

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?

Three short sentences, front-loaded with the resource and its payload, then the prerequisite, then a minimal call example — no filler. The inline slug example slightly duplicates the one already in the schema, a small redundancy.

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?

For a one-parameter, read-only lookup with a full output schema and full annotation coverage, the description covers what the tool is, what it returns, and how to obtain the required identifier. Nothing essential is missing; only minor edges (invalid-slug behavior, freshness semantics) are left implicit.

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

Parameters3/5

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

Schema description coverage is 100% and the slug property already carries the example and the 'as search returns it' framing, so the description's inline example adds little new meaning. Its real contribution is procedural ('find the slug with the search first') rather than semantic. Baseline 3 is appropriate when the schema does this much of the work.

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?

The description names the exact resource and its payload — 'One occupation's PERM record, with its SOC code and median offered wage, and its cases pending at DOL now' — so an agent knows the retrieval is per-occupation and what fields come back. It distinguishes itself from search_occupations by explicitly telling the caller to resolve the slug via search first. A verb is implied by the title rather than stated in the description, which keeps it just short of a 5.

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?

'Find the slug with the search first' is a concrete prerequisite that routes the agent to the search sibling before calling this tool, covering the main misuse risk (guessing a slug). It does not name the sibling tool or state when to use search_occupations vs. lookup_soc instead, so the guidance is clear but not fully exhaustive.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.