h1b-sponsor-mcp

Overview Schema Source Related Servers Discussions Admin

top_sponsors

Read-only

Rank employers by certified H-1B filings for a role and location, with denial-rate flags, to identify sponsorship options over a chosen look-back window.

Instructions

Rank employers by certified H-1B filings (with denial-rate flags), for a role and place.

Args:
    role: Optional job filter, e.g. "data scientist", "data engineer".
    state: Optional two-letter worksite state, e.g. "GA".
    city: Optional worksite city, e.g. "Atlanta".
    months: Look-back window in whole months ending at the latest data (1-21).
    limit: Number of employers to return (max 100).

Input Schema

Name	Required	Description	Default
`city`	No
`role`	No
`limit`	No
`state`	No
`months`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 29, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds genuinely new behavior context — the data source (certified H-1B filings), the presence of denial-rate flags, that the look-back window ends at the latest available data, and the max-limit boundary. It stops short of describing output shape, but an output schema exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core behavior is front-loaded in one sentence, and the Args block is a compact, scannable list with zero filler. Given the empty schema descriptions, each parameter line earns its place rather than restating structured data.

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 an output schema present, the description need not explain return values, and the read-only safety profile is already in annotations; together with full parameter semantics this is nearly complete. The only missing piece is how multiple filters combine and any guidance on choosing this tool versus its siblings.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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 it does: every one of the five parameters gets meaning plus concrete examples ('data scientist', 'GA', 'Atlanta') and hard bounds (months 1-21, limit max 100). Without this block an agent could not set 'months' or 'state' format correctly.

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 first sentence gives a concrete verb and resource — 'Rank employers by certified H-1B filings' — plus the scoping dimensions ('for a role and place') and an extra signal ('denial-rate flags'). An agent can distinguish this from a single-employer lookup like find_employer, though no sibling is named explicitly.

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 through 'for a role and place' and the optional parameters; there is no explicit statement of when to choose this over find_employer, company_sponsorship, or compare_companies. The reader must infer that this tool produces a ranked list rather than a single-company profile.

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

Deploy Server