Skip to main content
Glama

Salary, pay and hiring report

salary_and_hiring_report
Read-onlyIdempotent

The salary, pay, wages and hiring report for any job in any city, state or country: what a job pays, earns or makes, pay ranges, pay trends, job openings and demand. Same report as ask_gwix (use either, not both). GWIX's own analyst: answers a question with a full, sourced report that combines every relevant GWIX source (job ads, advertised pay, hiring) with official statistics (BLS, Census, ONS and other agencies), with percentiles, trends, comparisons, chart data, what it means, and a citation for every figure. Free Ask GWIX answers are used first; the result shows any credits used.

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": {
      "question": "<question>"
    },
    "name": "salary_and_hiring_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
placeNoWith occupation_code: the city with state (Houston, TX), metro or state in the question.
countryNoWith occupation_code and no place: ISO-2 country (US, GB).
questionYesThe user's question in their words, with any place, role, company, industry or period they gave.
occupation_codeNoWhen the question names a job: its SOC 2018 code, as soc_2018:29-1141 (registered nurses). Lets the GWIX panel show a quick summary while the report is written.

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 carry readOnly/idempotent/openWorld/non-destructive, and the description adds genuinely new behavior: combined GWIX data plus official statistics, every figure cited, free-answer quota consumed first, and credits shown in the result. It stops short of stating latency or report-size expectations.

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 capability, then the sibling relationship, then the report contents. The opening synonym chain ('pays, earns or makes... pay ranges, pay trends') is somewhat padded for discoverability but the rest of the text is dense and useful.

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?

No output schema exists, and the description compensates by enumerating what the report returns (percentiles, trends, comparisons, chart data, interpretation, citations). Combined with annotations covering the safety profile, only minor gaps (report length, cost magnitude) remain.

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 coverage is 100%, so all four parameters (including the occupation_code format and place/country pairing rules) are already documented. The description only implies these inputs via 'any job in any city, state or country', adding no format or precedence detail 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?

States a specific verb+resource (a sourced salary/pay/hiring report) and its scope (any job in any city, state or country), then names the interchangeable sibling ask_gwix so the agent can tell them apart without inspecting schemas.

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?

Explicitly says it is the same report as ask_gwix and to use either but not both, which is a real routing rule. It gives no guidance on when the narrower siblings (compare_pay_by_location, hiring_demand_report, pay_by_experience_level) should win instead.

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.