Skip to main content
Glama
Sign In

GWIX

by ai.gwix
OverviewDiscussionsAdmin

Compare pay across cities, states or countries

compare_pay_by_location
Read-onlyIdempotent

For comparing what a job pays in two or more places (cities, metros, states or countries), including remote or relocation questions. For a single place, 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": "compare_pay_by_location"
  }
}

Input Schema

NameRequiredDescriptionDefault
placeNoWith occupation_code: the city with state (Houston, TX), metro or state in the question.
placesNoThe places to compare, as the user named them (Houston, TX; Dallas-Fort Worth; Austin, TX).
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.3/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 genuinely new behavior: the tool acts as an analyst producing a full sourced report, blends GWIX data with BLS/Census/ONS statistics, cites every figure, and consumes free Ask GWIX answers before paid credits. It stops short of stating latency, limits on the number of places, or what happens if a place is unrecognized.

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 routing rule is front-loaded in the first sentence, which is the right structure. The second half drifts into promotional framing about 'GWIX's own analyst' and sourced reports; it carries real information about output and cost, but is longer than it needs to be for that content.

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 does the work of explaining the return: a full sourced report with percentiles, trends, comparisons, chart data, interpretation and citations. Combined with the credit-cost note, an agent knows what it will get back; only edge cases (invalid place names, max place count, failure modes) are unaddressed.

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 all five parameters are already documented in the schema, and the baseline of 3 applies. The description reinforces the geography semantics of 'places' but adds no syntax, ordering, or cardinality guidance beyond what the schema already says.

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 and resource ('comparing what a job pays in two or more places') and enumerates the geography types (cities, metros, states, countries) it covers. It also implicitly distinguishes itself from the single-place sibling, so an agent can tell the two apart without opening either schema.

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?

Explicitly names the triggering condition (two or more places, including remote/relocation questions) and names the alternative with its own condition: 'For a single place, use salary_and_hiring_report.' That is a textbook when/when-not routing rule.

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