Skip to main content
Glama

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

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered by structured data. The description adds genuinely non-structured behavior: the authoritative source (BLS JOLTS), a concrete per-call cost of $0.10, and a cryptographic attestation with a verification endpoint. What it does not disclose is data lag/frequency (JOLTS is a lagged monthly release) or latency, which matters for early-warning use.

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 lead sentence is front-loaded and dense with the right information — source, metrics, interpretation. The trailing attestation sentence ('Cryptographically attested with a post-quantum signed settlement receipt. Verify at trust.stratalize.com/verify.') is promotional boilerplate that consumes roughly a third of the text for provenance value an agent rarely acts on. The cost line is compact and useful; the marketing tail is not.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no parameters, no output schema, and read-only annotations, the description needs only to say what the agent gets back and under what conditions, which it largely does by listing the four returned measures. It omits geography (US-only BLS data is only implied by the acronym), reporting period/frequency, and whether the metrics are national aggregates or broken down by industry or region — gaps that affect whether an agent can safely rely on the result.

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 input schema declares zero properties, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly implies the tool takes no scoping input, which matches the 0-parameter schema and prevents an agent from inventing filter arguments.

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 specific data source and resource (BLS JOLTS) and enumerates the exact metrics produced: job openings, quits rate, layoffs rate, and a tight/loose/normal interpretation. An agent can tell this is a US labor-market indicator feed rather than a company or financial-data tool. It stops short of explicitly contrasting itself with any sibling, so sibling differentiation is inferred from topic alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Use cases are given as audience labels — workforce planning, wage pressure forecasting, recession early-warning agents — which implies when the tool is appropriate. However, there is no guidance on when NOT to use it, no named alternative among the many intelligence siblings (e.g., a sector or market brief), and no prerequisites such as needed context or expected cadence of the underlying data.

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