Skip to main content
Glama

get_salary_benchmark

Read-only

Use when setting compensation ranges, evaluating a job offer, or preparing a comp committee presentation for any role. Returns p25, p50, p75 wage estimates with state and industry adjustments across 50+ role families. Example: Software engineer in Illinois — p25 $98K, median $127K, p75 $158K — organizations benchmarking above p75 retain 34% fewer departures in competitive talent markets. Source: BLS Occupational Employment Statistics, latest release. $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": {
      "job_title": "<job_title>"
    },
    "name": "get_salary_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNoTwo-letter US state code
industryNoe.g. saas, healthcare, legal, financial_services, manufacturing, retail
job_titleYese.g. Software Engineer, CFO, Account Executive, Data Scientist, HR Manager

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the description's added value is what matters here: it discloses the data source (BLS OES latest release), the coverage breadth, the output shape, and a per-call price of $0.02 USDC. Pricing and provenance are genuinely useful beyond annotations; only latency/pagination behavior is unaddressed, which is minor for a single-lookup endpoint.

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 use case, then output shape, then a concrete worked example, then source and price — a sensible ordering. The retention statistic ('34% fewer departures') is persuasive filler rather than operational information and could be cut without losing anything.

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?

For a three-parameter, read-only lookup with no output schema, the description supplies everything an agent needs: inputs accepted, return fields, data provenance, cost, and breadth of coverage. There is no meaningful gap left for the agent to guess at.

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 the baseline would be 3, but the description adds real meaning: it clarifies that state and industry are adjustments applied to the benchmark (not just filters), and that job_title works for 'any role' across 50+ role families. That reframes how an agent should supply optional parameters rather than merely repeating 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?

States a specific outcome (compensation benchmarking for a role) plus exactly what is returned: p25/p50/p75 wage estimates with state and industry adjustments across 50+ role families. An agent can immediately distinguish this from regulatory, commodity, or company-disclosure benchmarks in the sibling list.

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?

Gives three concrete triggering scenarios — setting comp ranges, evaluating an offer, preparing a comp committee deck — which is stronger than most definitions. It stops short of naming an alternative (e.g. get_company_salary_disclosure) or stating when this market-benchmark data is the wrong choice, so it is clear context without exclusions.

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