Skip to main content
Glama

Get a law firm's PERM record

get_law_firm
Read-onlyIdempotent

One law firm's PERM record from DOL's published files, and how many of its cases are pending at DOL now, by stage. Find the slug with the search first. Example: {"slug":"fragomen-del-rey-bernsen-loewy-llp"}.

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

Input Schema

NameRequiredDescriptionDefault
slugYesThe name in its page's address, as search returns it. Example: fragomen-del-rey-bernsen-loewy-llp.

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.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds useful provenance (DOL published files) and the nature of the pending-case breakdown, but says nothing about freshness, pagination, or lookup failure behavior beyond what the output schema implies.

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?

Four short sentences, front-loaded with the resource and followed by the prerequisite. The trailing example restates the schema example verbatim, which is minor waste but not harmful.

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 one required, fully documented parameter and an output schema covering return values, the description needs only to establish scope and the slug prerequisite, which it does. Nothing essential is missing for an agent to call it correctly.

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 coverage is 100% and the slug parameter already documents its meaning and example. The description's 'find the slug with the search first' adds procedural meaning about where the value comes from, but the duplicated example is redundant, so this sits at the baseline.

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?

Names the specific resource (one law firm's PERM record from DOL's published files) and even what the response contains (pending case counts by stage). It distinguishes itself from the search sibling only indirectly through the 'find the slug first' sentence rather than an explicit contrast, so it stops 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?

Explicitly states the prerequisite workflow: 'Find the slug with the search first,' which routes the agent to search_law_firms before calling this. There is no explicit when-not guidance, but for a by-ID lookup tool the usage context is clear.

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.