Skip to main content
Glama

get_bls_sector_employment

Read-only

Use when benchmarking workforce planning against sector labor market conditions, assessing industry growth trajectory for strategic planning, providing economic context for board reporting, or evaluating talent acquisition timing for a specific industry. Returns BLS payroll employment by major sector with month-over-month change, year-over-year change, and trend classification from the official establishment survey covering 650,000 US worksites — the same data the Federal Reserve uses to assess labor market conditions. Example: Healthcare sector — 8.41M employed, +47K MoM, +3.2% YoY, EXPANDING for 14 consecutive months — persistent hiring demand supports above-market compensation benchmarks. Source: Bureau of Labor Statistics Current Employment Statistics. $0.10 USDC per call.

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": {
      "sector": "<sector>"
    },
    "name": "get_bls_sector_employment"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectorYes

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=true and destructiveHint=false, and the description adds real behavioral context beyond them: authoritative public source, coverage scope, trend classification semantics, a worked example with interpretation, and an explicit per-call cost of $0.10 USDC. It does not describe latency, caching, or data freshness beyond '14 consecutive months' in the example.

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 description is front-loaded with the use case and the return payload before the example, source, and price, so an agent gets the essentials immediately. The four-scenario opener and the interpretive commentary inside the example are somewhat padded, but each block still carries usable information.

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 only one parameter and no output schema, the description carries the burden of describing returns, and it does so by naming the three derived metrics plus a concrete example. Minor gaps remain around output shape/units and the semantics of the 'all_private' enum value.

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?

There is a single required parameter with a nine-value enum but no schema descriptions (0% coverage). The description shows one mapping in the example (Healthcare), which implicitly explains the sector parameter, but it never clarifies the crucial 'all_private' aggregate option or the coverage scope of values like 'government' and 'financial_services'.

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 description states a specific resource (BLS payroll employment by major sector) and exactly what is returned: month-over-month change, year-over-year change, and trend classification. It also names the underlying source (Current Employment Statistics, 650,000 worksites), which lets an agent distinguish it from related labor-cost tools like the employment cost index without opening the schema.

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?

Four concrete usage scenarios are given (workforce planning benchmarks, industry growth trajectory, board reporting, talent acquisition timing), which is clear when-to-use context. It does not name a sibling alternative or state when NOT to use it (e.g., versus wage/cost indices), so it stops short of full routing guidance.

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.

Resources