Skip to main content
Glama
h1b-sponsor-mcp

h1b-sponsor-mcp

by janishkumar

company_sponsorship

Read-only

Check whether a company still sponsors H-1B visas and review six-month, fiscal-year, PERM, and USCIS approval/denial trends by role, state, or city.

Instructions

Is a company still sponsoring H-1Bs, and how much? Returns trend tables.

Shows certified H-1B LCA filings for the last 6 months, the fiscal year so far and the
last full fiscal year (each vs the same period a year earlier), split into new
employment and transfers; green-card (PERM) certifications; USCIS petition
approvals/denials by fiscal year; and a denial-rate flag (Normal / Elevated / High)
relative to the national rate. Point out a High or Elevated flag to the user.

Args:
    company: Employer name as people say it, e.g. "Microsoft", "Amazon", "JPMorgan".
    role: Optional job filter, e.g. "data scientist", "machine learning",
        "software engineer". Matches job title and occupation title.
    state: Optional two-letter worksite state, e.g. "GA".
    city: Optional worksite city, e.g. "Atlanta".

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

Input Schema

NameRequiredDescriptionDefault
cityNo
roleNo
stateNo
companyYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish a safe read operation (readOnlyHint=true, openWorldHint=false), so the bar is lower, and the description adds real value on top: it discloses the comparison structure (each period vs the same period a year earlier), the split into new employment vs transfers, and the Normal/Elevated/High denial-rate categorization with a directive to surface elevated results. What it does not cover — caching, data recency cutoff beyond 'last 6 months' — is minor for a read-only 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?

Front-loaded with the user-facing question, followed by the return scope, then a clean Args block. The middle enumeration is dense and semicolon-chained, and the fragment 'Returns trend tables.' adds little given the detail that follows, but nothing is wasted overall.

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?

Although an output schema exists and return values need not be spelled out, the description supplies enough about the returned periods, breakdowns, and denial-rate flag for an agent to interpret and act on results. All four parameters are documented and the one required parameter is obvious from the schema.

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 description coverage is 0%, so the description must carry the full burden and largely does: it explains that 'company' should be the employer name as people say it with three concrete examples, that role matches both job title and occupation title, and that state/city are worksite filters with format examples. Only minor gaps remain (no guidance on partial vs exact company matching behavior).

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?

Opens with the exact question the tool answers ('Is a company still sponsoring H-1Bs, and how much?') and then enumerates the specific artifacts returned: H-1B LCA filings by period, PERM certifications, USCIS petition approvals/denials, and a denial-rate flag. This is distinguishable from siblings like top_sponsors or compare_companies, which imply ranking or multi-employer comparison rather than single-employer trend detail.

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?

The question framing gives clear context for when to invoke it (a single-company sponsorship question), and it adds an explicit behavioral instruction: 'Point out a High or Elevated flag to the user.' It stops short of naming when to prefer a sibling such as compare_companies for multi-employer questions, so it is clear context without explicit exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.