Skip to main content
Glama

Match an employer's name to its page

lookup_employer
Read-onlyIdempotent

The employer page a printed name belongs to: an exact match, a possible one with the matched name, or none. It comes with the employer's PERM decisions, certified share, pending cases, newest filing and H-1B LCAs. No key: it's what the browser extension calls, under shared limits of 60 calls a minute per address. Example: {"name":"Google"}.

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe employer's name as a job posting prints it, 2 to 120 characters. Example: Google.

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
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), but the description adds genuinely new operational facts: no API key is required, and there is a shared limit of 60 calls per minute per address. It also previews the payload that comes back with the page (PERM decisions, certified share, pending cases, newest filing, H-1B LCAs), which tells the agent this is a one-shot enrichment call rather than a bare ID lookup.

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?

Compact and front-loaded, with the core resolution behavior in the first sentence and the rate limit appended where it belongs. The trailing JSON example duplicates the schema's own example, and the telegraphic style ('No key: it's what the browser extension calls') costs a little readability.

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 single-parameter read tool with an output schema and full annotation coverage, this covers the important gaps: authentication posture, rate limiting, and the ambiguity of name matching. Return-value detail is arguably redundant given the output schema, but it is not harmful. The main omission is guidance on next steps when the result is 'possible' or 'none'.

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%, so the baseline is 3, and the schema already states the format, length bounds and example. The description nonetheless adds matching semantics the schema does not convey: the input may match exactly, may match only tentatively (returning the matched name for confirmation), or may not match at all. That changes how an agent should interpret and act on the parameter's result.

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 states a concrete transformation: a printed employer name resolves to 'the employer page,' with three named outcomes (exact match, possible match with the matched name, none). That is far more specific than a restatement of the name. It never names or contrasts with the plausible siblings (search_employers, get_employer), so sibling differentiation is left to inference.

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

Usage Guidelines2/5

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

Usage is only implied: you supply a name 'as a job posting prints it' and get a resolution. There is no statement of when to prefer this over search_employers or get_employer, nor what to do when the result is 'possible' or 'none'. The only routing information is that a browser extension is the caller, which does not help an agent choose.

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.