Skip to main content
Glama

Get a case by its number

get_case
Read-onlyIdempotent

One case by number: its status, filing date, employer and, once decided, DOL's record. Covers PERM, prevailing wage, H-1B LCA and H-2A, H-2B and CW-1 (applications, job orders and wage requests). A seasonal case adds its workers, work period and worksite, and the job as DOL accepted it. A pending PERM case adds its filing month's place in the queue. Example: {"caseNumber":"G-100-26045-123456"}.

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": {
      "caseNumber": "<caseNumber>"
    },
    "name": "get_case"
  }
}

Input Schema

NameRequiredDescriptionDefault
caseNumberYesAs DOL prints it: G-100-... for PERM, P-100-... for a prevailing wage request, I-200-... for an H-1B LCA, H-300-..., H-400-..., JO-A-300-... or C-500-... for the seasonal programs. Example: G-100-26045-123456.

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 carry the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the description is free to spend its words on behavior that matters: it discloses that response content is conditional — seasonal cases add workers/work period/worksite, pending PERM cases add queue position, and DOL's record only appears once decided. That conditional-shape disclosure is genuine added context, though it says nothing about what happens when a case number matches nothing.

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 the essential fact ('One case by number') followed by what comes back, with the program-code enumeration and the example at the tail where they are easy to skim. The parenthetical program list is dense but each item earns its place by telling the agent which case types resolve; only the duplicated example keeps it from being maximally tight.

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?

With a single fully documented required parameter, a complete annotation set, and an output schema handling return shape, the description covers what an agent needs to select and call it. The only meaningful gap is not-found or invalid-format behavior, which the description leaves unanswered.

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 schema itself already lists the accepted case-number prefixes and an example, so the description does not need to re-explain the parameter. The trailing example call adds a small amount of invocation clarity but largely restates the schema's own example format, keeping this at the baseline.

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 names a specific verb+resource ('One case by number') and immediately enumerates the payload (status, filing date, employer, DOL record), which clearly separates it from the search/list siblings such as find_cases and get_employer. It also scopes the covered visa programs, so an agent knows exactly what entity universe this returns.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: 'One case by number' signals an exact-identifier lookup rather than a search, but the description never explicitly says when to use this instead of find_cases or what to do when the case number is unknown. There are no stated prerequisites or exclusions, so the agent must infer the retrieval pattern from the phrase and the example.

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.