Skip to main content
Glama
Sign In

GWIX

by ai.gwix
OverviewDiscussionsAdmin

Workforce turnover report: quits, separations and tenure

workforce_turnover_report
Read-onlyIdempotent

For turnover, quit rates, separations, tenure and intent to leave in an industry, occupation or place. GWIX gives actual quits and separations from official statistics; survey data on intent to leave is not covered yet, and the report says so. 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": "workforce_turnover_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

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description's value is in what it adds: source provenance (BLS, Census, ONS plus GWIX job ads and pay data), a citation for every figure, a disclosed coverage gap, and the credit-consumption model with free Ask GWIX answers applied first. That is substantive beyond the annotations, though it doesn't say anything about latency, report length, or failure modes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is well front-loaded and earns its place. The remainder is a long, generic block about the GWIX analyst pipeline and credit handling that is boilerplate across the report family and could be trimmed without losing tool-specific signal.

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 correctly compensates by describing report contents (percentiles, trends, comparisons, chart data, interpretation, per-figure citations) and the free-answer/credit mechanic. What remains unstated — typical report size or turnaround — is minor for a read-only report generator.

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 baseline is 3 and the schema already explains place, country, occupation_code and question precedence. The description's mention of 'industry, occupation or place' loosely maps to those parameters but adds no syntax, precedence rules, or formatting detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence names specific topics (turnover, quit rates, separations, tenure, intent to leave) and the scoping dimensions (industry, occupation, place), which lets an agent separate it from generic siblings like labor_market_report or talent_supply_report. However, the second half describes the generic 'GWIX analyst' report behavior shared by hiring_demand_report, salary_and_hiring_report and others, so no sibling is named explicitly as an alternative.

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?

The lead phrase 'For turnover, quit rates, separations, tenure and intent to leave' functions as a clear trigger condition, and the description adds a scope exclusion ('survey data on intent to leave is not covered yet'), which is genuine when-not guidance. It stops short of naming a sibling to use instead for that excluded data.

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