Skip to main content
Glama

get_company_salary_disclosure

Read-only

Use when benchmarking compensation against disclosed employer wages or assessing H-1B wage practices before a talent acquisition or competitive hire. Returns DOL LCA and H-1B wage aggregates by employer, job title, state, and fiscal year. Example: Microsoft H-1B software engineer — prevailing wage Level III $178K in Seattle, Level IV $215K — 847 certified positions in 2023, concentrated in Washington and California. Source: DOL Office of Foreign Labor Certification public filings. $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": {
      "company_name": "<company_name>"
    },
    "name": "get_company_salary_disclosure"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNo
job_titleNo
fiscal_yearNo
company_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, non-destructive, open-world access, yet the description still adds real context: the underlying source (DOL OFLC public filings), the aggregation dimensions, a concrete illustrative result, and a per-call price of $0.02 USDC. It stops short of coverage caveats such as only certified positions or filing-year lag, which would matter for interpreting the aggregates.

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?

Front-loaded with the usage trigger, followed by return shape, a concrete example, source, and price in a logical order. The worked example is longer than strictly necessary but earns its place by showing output granularity that no schema documents.

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 read-only lookup with no output schema and four undocumented parameters, the description supplies source, aggregation grain, an example result, and cost — enough to call it correctly and to judge the spend. The remaining gap is filter format and default behavior when only company_name is supplied.

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 0%, so the description must carry the load, and it does map each parameter to a dimension (employer, job title, state, fiscal year). However it gives no format guidance — whether state is an abbreviation or full name, whether fiscal_year is an integer like 2023 or a range, or what happens when optional filters are omitted.

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?

States a specific verb and resource: returns DOL LCA and H-1B wage aggregates by employer, job title, state, and fiscal year, sourced from DOL OFLC filings. The H-1B/LCA framing is distinctive, but the description never names or distinguishes itself from the close sibling get_salary_benchmark, so an agent comparing the two must infer the boundary.

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?

Opens with an explicit use case: benchmarking compensation against disclosed employer wages or assessing H-1B wage practices before a talent acquisition or competitive hire. That gives a clear context for selection, but there is no when-not guidance and no named alternative for general (non-disclosure) salary benchmarking.

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