Skip to main content
Glama

US H-1B Visa Sponsors MCP

employer_detail

PRO. All rows for an employer (each location/tax ID) with approval rate.

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

Input Schema

NameRequiredDescriptionDefault
employerYes
access_tokenNoSubscriber token from /success (or Authorization: Bearer)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.5/5.0
Behavior2/5

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

No annotations, so the description carries the full behavioral burden. 'PRO' hints at a paid/subscriber requirement and the access_token schema description corroborates that, but there is no mention of rate limits, cost, result size, or pagination for what is described as 'all rows' for an employer.

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

Conciseness3/5

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

Extremely short with zero filler, and the output granularity is front-loaded. However, the 'PRO.' token is unexplained jargon that consumes attention without conveying behavior, and the brevity comes at the cost of specification.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter lookup with no annotations and no output schema, the agent still cannot tell the data source, whether results are paginated or capped, or what 'approval rate' means. More disclosure is required before an agent can invoke this with confidence.

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 50%: access_token is documented in the schema, while 'employer' has no description. The description implies the employer argument drives the lookup but never says whether it is a name, ticker, or ID, or whether matching is exact or fuzzy — the same coverage gap remains.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

It identifies the resource (an employer's records) and the output granularity (each location/tax ID) plus the enrichment (approval rate), which is more than a restatement of the name. But 'rows' is never defined — the agent must guess the data domain (H-1B/LCA filings implied only by siblings) and there is no explicit differentiation from h1b_check or sponsor_search.

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?

No statement of when to use this instead of h1b_check or sponsor_search, and no guidance on prerequisites beyond the opaque 'PRO' prefix. The agent must infer from context that this is the detailed, subscription-gated alternative.

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.