Skip to main content
Glama
satovarb16
by satovarb16

check_visa_sponsorship

Check a company's H-1B visa sponsorship history using real USCIS data to avoid applying to roles that won't sponsor visas.

Instructions

Check H-1B visa sponsorship history for a company via USCIS Employer Hub.

Pass the full employer name exactly as it appears in the job posting (e.g. 'Google LLC', 'Amazon Web Services', 'Microsoft Corporation'). Abbreviated names like 'Meta' or 'Amazon' may match subsidiaries instead of the primary entity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
companyYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceNoUSCIS H-1B Employer Hub FY2024
companyYes
verdictYes
approval_rateYes
total_filingsYes
Behavior3/5

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

Discloses the data source (USCIS Employer Hub) and the importance of name accuracy, but does not mention read-only nature, rate limits, or authentication requirements, which is a gap given no annotations.

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?

Three sentences with no redundant information; the key point about the company name format is front-loaded.

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?

Covers the main usage and a common pitfall; output schema exists so return values need not be described. Could mention prerequisites like a USCIS account, but overall adequate.

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?

Adds significant meaning beyond the schema by instructing to use the full employer name and warning about abbreviations, compensating for the 0% schema description coverage.

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?

Clearly states the tool checks H-1B visa sponsorship history via USCIS Employer Hub, which is distinct from sibling tools focused on jobs and profiles.

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?

Provides clear guidance to pass the full employer name exactly as in the job posting and warns about abbreviations, though no explicit when-not to use is given.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/satovarb16/runwayMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server