Skip to main content
Glama
Sign In

GWIX

by ai.gwix
OverviewDiscussionsAdmin

Job offer check: is this pay competitive?

job_offer_check
Read-onlyIdempotent

For setting or judging a job offer: what to offer or ask for, whether an offer or a current salary is competitive, and where it sits in the market for the job, level and place. For a general question about what a job pays, use 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": "job_offer_check"
  }
}

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.
job_levelNoentry, intermediate or senior, if the user said (years of experience map to these).
pay_periodNoyear (default) or hour.
offer_amountNoThe offer or salary to judge, if one was given, per year unless pay_period says otherwise.
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.3/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent and non-destructive, so safety is covered; the description adds genuinely new context – that a full sourced report is produced from GWIX data plus official statistics, with a citation per figure, and that free Ask GWIX answers are consumed first with credits shown. It stops short of describing latency or how partial data is handled.

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?

Use case is front-loaded in the first clause and the alternative is stated early. The second sentence is a long run-on packing sourcing, percentiles, trends, chart data and credit behavior together, which could be broken up, but little is wasted.

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?

With no output schema, the description carries the burden of describing what comes back and does so (sourced report, percentiles, trends, comparisons, chart data, citations, credit usage). Minor gaps remain around how quickly the quick-summary versus full report resolves, but an agent has what it needs to call 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 the seven parameters are already well documented (place, country, occupation_code, offer_amount, pay_period, job_level). The description only loosely gestures at them via 'the job, level and place', adding little beyond the schema, 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?

States a specific task (setting or judging a job offer), lists the concrete sub-questions it answers (what to offer or ask for, whether an offer or current salary is competitive, market position), and explicitly names the sibling it is not (salary_and_hiring_report). An agent can route on this alone.

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?

Gives an explicit exclusion with the alternative: 'For a general question about what a job pays, use salary_and_hiring_report.' The competitive/specific-offer use case is clearly bounded against the general-pay sibling.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All GWIX toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources