Skip to main content
Glama

get_employer_h1b_wages

Read-only

Use when analyzing an employer H-1B compensation strategy or benchmarking tech sector wages against DOL prevailing wage data. Returns prevailing wage statistics, certified job titles, wage levels, and state distribution from DOL LCA filings. Example: Google H-1B — software engineer Level IV prevailing wage $195K, 1,243 certified positions in 2023 — concentrated in Mountain View and New York City offices. Source: DOL Labor Condition Application public data. $0.02 USDC per call.

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_name": "<employer_name>"
    },
    "name": "get_employer_h1b_wages"
  }
}

Input Schema

NameRequiredDescriptionDefault
employer_nameYese.g. Google, Deloitte, Cognizant

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

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, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds value beyond that by naming the upstream data source (DOL LCA public data), summarizing the returned fields, and disclosing a per-call cost of $0.02 USDC, which matters for invocation decisions. It does not discuss rate limits or data vintage beyond the 2023 example.

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?

Usage guidance is front-loaded, followed by return contents, a concrete example, source, and price — a logical order with little waste. The example sentence is long and somewhat illustrative rather than informational, but it earns its place by showing output shape.

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?

For a one-parameter, no-output-schema tool with annotations covering safety, the description does the heavy lifting on return values, data provenance, and cost. The remaining gap is name-matching semantics and whether results cover a fixed or selectable time window.

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 description coverage is 100% and the single parameter already carries examples (Google, Deloitte, Cognizant), so the baseline is 3. The description's employer example (Google) mirrors the schema and does not clarify matching behavior — e.g. whether employer_name must be an exact legal-entity match or supports partial names.

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 names a specific verb and resource set — returns prevailing wage statistics, certified job titles, wage levels, and state distribution from DOL LCA filings — so an agent knows exactly what the tool produces. It also distinguishes itself from the benchmark/regulatory siblings by scoping to employer-level H-1B wage data.

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?

It explicitly says when to use it: analyzing an employer H-1B compensation strategy or benchmarking tech wages against DOL prevailing wage data. There are no explicit when-not conditions or named alternatives, but the trigger context is clear enough for selection.

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.

Resources