Skip to main content
Glama
Sign In

GWIX

by ai.gwix
OverviewDiscussionsAdmin

Talent supply report: size of the talent pool

talent_supply_report
Read-onlyIdempotent

For how many people work in an occupation in a place, the size of the talent pool, and whether workers are moving in or out. For hiring demand, use hiring_demand_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": "talent_supply_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 declare readOnlyHint, idempotentHint, and openWorldHint, so safety is covered. The description adds real value beyond that: it discloses the composition of the report (multiple GWIX sources plus official statistics), that every figure is cited, and the credit-consumption behavior ('Free Ask GWIX answers are used first; the result shows any credits used').

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 core question ('for how many people work...') and the sibling exclusion are front-loaded before the longer capabilities sentence. The second sentence is a dense list of report components, but each item informs what the agent will get back, so it earns its space.

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 the return value and does so (percentiles, trends, comparisons, chart data, interpretation, citations). Combined with 100% schema coverage, an agent has enough to invoke correctly; only the relationship to other report siblings is thin.

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 four parameters are already documented in the schema, including the place/country/occupation_code interplay. The description only echoes 'in an occupation in a place' and adds no format or precedence detail beyond what the schema states, so 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 verb and resource: workforce size in an occupation and place, plus talent-pool flows (workers moving in or out). This is clearly distinguishable from hiring_demand_report and the other report siblings, which cover different facets of the labor market.

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 routes hiring-demand questions to hiring_demand_report, which is the most confusable sibling. It does not differentiate from labor_market_report, salary_and_hiring_report, or workforce_turnover_report despite their overlap, so the exclusions are only partially covered.

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