Skip to main content
Glama
Sign In

Perm

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Perm Top Sponsors

perm_top_sponsors
Read-onlyIdempotent

Find which US employers sponsor the most green cards (PERM labor certifications) for a given job title (optionally in a specific city) — a candidate-sourcing / target-account signal for recruiting. Answers 'which companies sponsor the most data engineers for green cards' or 'top PERM sponsors for nurses'. Returns employers ranked by certified PERM filings for the role, each with their filing count and median offered wage. Backed by real DOL PERM disclosures.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "year": 2025,
      "job_title": "nurse"
    },
    "name": "perm_top_sponsors"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoOptional worksite city to scope to, e.g. "AUSTIN" or "NEW YORK".
yearNoFiling year (e.g. 2025). Defaults to the most recent full year.
limitNoMax employers to return (default 15, max 50).
job_titleYesJob title to rank sponsors for, e.g. "data engineer", "physical therapist".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower. The description adds real behavioral context beyond them: ranking is by certified PERM filings (not all filings), each row carries filing count and median offered wage, and the data source is DOL PERM disclosures. It doesn't discuss result limits or freshness beyond the year default, which is already in schema.

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?

The core purpose and scope are front-loaded, and the trailing sentences on return shape and provenance are informative. The two quoted example questions partly restate the opening sentence, so there is minor redundancy rather than waste.

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?

There is no output schema, and the description compensates fully by describing the return: employers ranked by certified PERM filings, each with filing count and median offered wage. Combined with defined defaults for year and limit in the schema, an agent has everything needed to call and interpret this tool.

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% with descriptions for all four parameters, so the baseline of 3 applies. The description reinforces that city is an optional scoping dimension and that job_title drives ranking, but adds no format or edge-case guidance (e.g., title matching behavior, city case sensitivity) beyond the schema.

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: 'find which US employers sponsor the most green cards (PERM labor certifications) for a given job title', with optional city scoping. This is clearly distinguishable from sibling tools like perm_employer_certifications (employer-centric) and perm_salary (wage-centric), since it ranks employers by job title.

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?

Frames the use case explicitly ('candidate-sourcing / target-account signal for recruiting') and gives two concrete example questions. It lacks an explicit 'use this instead of X when...' routing statement against its PERM siblings, 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.

All Perm toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources