Skip to main content
Glama

Get an employer's PERM record

get_employer
Read-onlyIdempotent

One employer's PERM record: cases, certified and denied, median days to decision, filings in the last 12 months, and how many of its cases are pending at DOL now, by stage. Find the slug with the search first. Example: {"slug":"google-llc"}.

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_employer"
  }
}

Input Schema

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

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

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so safety is fully covered. The description adds the substantive detail that the record is employer-aggregated and time-bounded (12 months, current DOL pending by stage), but says nothing about result size, pagination, or empty/miss behavior. Useful context on top of annotations, not rich behavioral disclosure.

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?

Three short sentences, payload description front-loaded, prerequisite second, concrete example last. Nothing is padding; the JSON example reinforces the required key without restating the schema.

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?

For a one-parameter, read-only lookup with a published output schema and full annotation coverage, everything the agent needs to call it correctly is present — what comes back, the prerequisite to obtain the slug, and the shape of the request.

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 100% and the schema already documents the single slug field with an example, so the baseline is 3. The description goes one step further by explaining where the value must come from — the search tool — turning the parameter into a required two-step lookup rather than a free-form key.

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?

States a specific verb and resource ("One employer's PERM record") and enumerates the payload — cases certified and denied, median days to decision, trailing-12-month filings, pending stages — which clearly scopes it as employer-level rather than case-level like get_case. An agent can distinguish it from siblings without opening a schema.

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" gives a concrete workflow prerequisite, so the agent knows this tool cannot be called cold with an employer name. It stops short of naming an alternative tool or stating exclusions, which keeps it below a 5.

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.