Skip to main content
Glama

H1b

by io.github.pipeworx-io
OverviewDiscussionsAdmin

H1b Salary

h1b_salary
Read-onlyIdempotent

Look up real H-1B base salaries for a job title from DOL LCA disclosures — a market wage benchmark backed by actual filed salaries (not estimates). Answers 'what do H-1B software engineers earn at company X / in city Y'. Filter by job title, and optionally by employer, city, and year. Returns salary statistics (count, min / median / average / max) plus a sample of individual records (employer, title, salary, location, dates).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoOptional work city, e.g. "SEATTLE" or "NEW YORK".
yearNoFiling year (e.g. 2024). Defaults to the most recent full year.
limitNoMax sample records to return (default 15, max 50).
employerNoOptional employer name to scope to, e.g. "Meta".
job_titleYesJob title to search, e.g. "software engineer", "data scientist". Matched as a substring of the disclosed title.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "city": "SEATTLE",
+    "employer": "Meta",
+    "job_title": "software engineer",
+    "year": 2024
+  },
+  {
+    "job_title": "data scientist",
+    "limit": 25
+  }
+]
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations (readOnlyHint, idempotentHint, etc.) already convey safety; the description adds valuable context: data is from actual filings, not estimates, and returns statistics plus sample records.

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 description is concise and front-loaded, covering purpose, data source, filtering, and output in a few clear sentences without excess.

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?

Despite no output schema, the description fully explains the return value (salary statistics + sample records), making the tool's output predictable.

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 coverage is 100%, so baseline is 3. The description adds extra meaning: job_title matched as substring, year defaults to most recent, limit default 15 max 50. This goes 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?

The description clearly states the tool looks up real H-1B base salaries from DOL LCA disclosures, distinguishing it from sibling tools like h1b_employer_sponsorship and h1b_top_sponsors.

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 description explicitly answers what the tool does and provides filtering options (job title required, optional employer/city/year). It implicitly shows when to use it but lacks explicit 'when not to use' or alternatives.

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

All H1b 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