Skip to main content
Glama

Company hiring and pay report

company_hiring_report
Read-onlyIdempotent

For what a named company is hiring for, how its hiring is shifting between functions or countries, and how its advertised pay compares with its market. For a whole market, use hiring_demand_report or salary_and_hiring_report. 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": "company_hiring_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
placeNoWith occupation_code: the city with state (Houston, TX), metro or state in the question.
companyNoThe company or ticker as the user named it.
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.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered; the description adds substantive behavior beyond that — synthesis of job ads, advertised pay, hiring data plus BLS/Census/ONS statistics, percentile and trend output, chart data, and a citation for every figure. It stops short of describing report length, latency, or what happens on an ambiguous company name, so it is strong rather than complete.

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 scope and the sibling exclusion are front-loaded, and no sentence is filler. The third sentence is a long compound list of output characteristics that could be tightened, but each clause carries real information about what the report returns.

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?

With no output schema, the description carries the burden of explaining returns, and it does: full sourced report, percentiles, trends, comparisons, chart data, interpretation, per-figure citations, and credit usage. Combined with annotations covering the safety profile and 100% schema coverage on inputs, an agent has what it needs to call this correctly.

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%, so every parameter including the place/occupation_code/country interplay is already documented in the schema. The description implies a company focus but adds no format or precedence guidance (for example, how company interacts with occupation_code) beyond what the schema states, so the baseline 3 applies.

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 opening sentence gives a specific verb+resource+scope: hiring mix, hiring shifts by function/country, and advertised pay versus market, scoped to a named company. That scope immediately separates it from market-wide siblings like hiring_demand_report, and the follow-up sentence clarifies it is an analyst-authored, fully sourced report rather than a raw data lookup.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the selecting condition (a named company) and explicitly routes the whole-market case to hiring_demand_report or salary_and_hiring_report by name. It also discloses the cost/credit behavior up front (free Ask GWIX answers used first, credits shown), which is exactly the kind of pre-call guidance an agent needs before invoking an expensive tool.

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.