Skip to main content
Glama

Stratalize Intelligence

Get Job Openings Intelligence

get_job_openings_intelligence
Read-only

JOLTS labor market intelligence from BLS: job openings, quits rate, layoffs rate, and tight/loose/normal interpretation. Use for workforce planning, wage pressure forecasting, and recession early-warning agents. Source: BLS JOLTS. $0.10 standard. Cryptographically attested with a post-quantum signed settlement receipt. Verify at trust.stratalize.com/verify.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_job_openings_intelligence"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, openWorld, non-destructive), yet the description adds genuinely non-obvious behavior: the upstream source (BLS JOLTS), a concrete price point ($0.10 standard), and a cryptographic settlement receipt with a verification URL. These are facts an agent could not infer from structured fields. It does not describe latency, freshness/cadence of the JOLTS series, or failure modes, which keeps it out of the top tier.

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?

It is front-loaded with what the tool returns, then use cases, then provenance and pricing — a sensible ordering with no filler sentences. The attestation sentence is marketing-flavored and slightly verbose, but it does carry verification information, so it earns partial credit rather than being pure padding.

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 input parameters and no output schema, the description's job is to convey what comes back and why to call it, and it lists the metric set plus intended use cases. The absence of any output schema means response shape (fields, historical depth, geography scope) is left unstated, a minor but real gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. The description instead specifies what the output covers, which is the useful analogue here.

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 description names a concrete resource and source (JOLTS labor market data from BLS) and enumerates the specific metrics returned: job openings, quits rate, layoffs rate, and a tight/loose/normal interpretation. That is far more specific than a restated title. It stops short of explicitly contrasting itself with sibling intelligence tools, but the topic framing makes the domain unambiguous.

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 explicit use contexts — workforce planning, wage pressure forecasting, recession early-warning agents — which tells an agent when this tool is the right pick. There are no exclusions or named alternatives for overlapping cases, so it falls short of the 5 tier.

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