Skip to main content
Glama

Stratalize Healthcare

Get Company Salary Disclosure

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
  2. Removed
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With readOnlyHint and openWorldHint already supplied, the description still adds real value: the upstream source (DOL Office of Foreign Labor Certification public filings), the aggregate dimensions returned, and a per-call cost of $0.02 USDC. It does not describe latency, result caps, or what happens when a company has no filings, which keeps it below a 5.

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?

The trigger condition is front-loaded and the pricing is a tight closing sentence. The worked Microsoft example is long but serves as a compressed output preview, so it earns most of its space.

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, single-call lookup with no output schema, the description covers source, returned dimensions, an illustrative result, cost and use case. The remaining gap is parameter format guidance, which is notable at 0% schema coverage but not disqualifying.

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 carries the burden, and it partially does by mapping the four parameters to employer, job title, state and fiscal year. It adds no format detail — state codes vs names, fiscal year representation, or how company_name is matched.

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?

The description names a specific resource and scope: DOL LCA and H-1B wage aggregates by employer, job title, state and fiscal year. That is clearly narrower than a generic salary benchmark, though the text never explicitly contrasts itself with the sibling get_salary_benchmark, leaving the distinction to inference.

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 gives clear situational triggers — benchmarking against disclosed employer wages, assessing H-1B wage practices, pre-acquisition or competitive-hire research. There is no explicit when-not guidance or named alternative for general market compensation, so the agent must infer that this tool only covers disclosed filings.

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