Skip to main content
Glama

Stratalize Intelligence

Get Bls Sector Employment

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?

The annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true). The description adds real behavioral context beyond them: the upstream source (BLS Current Employment Statistics), the scale of the survey (650,000 worksites), the specific derived fields returned, and a per-call price of $0.10 USDC. What it does not state is the time coverage or latency, so it falls short of a 5.

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 a 'Use when' clause, then the return fields, then source, example, and cost, which is a sensible order. The illustrative example is slightly padded with marketing-flavored commentary ('supports above-market compensation benchmarks'), but no sentence is wholly 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?

For a one-parameter read tool with no output schema, the description covers the source, returned fields, trend classification, and cost, which is close to what an agent needs. The remaining gap is temporal scope: it does not say whether it returns only the latest month or a historical series, which matters for the stated benchmarking use cases.

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 0% schema description coverage, but its enum self-documents the eight allowed sector values. The description only illustrates one value ('Healthcare sector') and does not clarify ambiguous entries such as 'all_private' (an aggregate, not a sector) or how 'technology' is defined, so it adds little meaning beyond the enum.

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 names a specific verb and resource: it 'Returns BLS payroll employment by major sector with month-over-month change, year-over-year change, and trend classification.' That is a precise, distinguishable payload that separates it from siblings such as get_bls_inflation_components, even though no sibling is named.

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?

It gives four concrete when-to-use contexts: workforce benchmarking, industry growth assessment, board reporting, and talent acquisition timing. That is clear context, but there are no exclusions, prerequisites, or guidance about when a different labor-market tool (for example the employment cost index) would be the better choice.

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