Skip to main content
Glama

Stratalize Intelligence

Get Labor Market Benchmark

get_labor_market_benchmark
Read-only

Live labor market benchmarks from FRED — unemployment, U-6 underemployment, JOLTS job openings, quit rate, labor participation, weekly claims, wage growth. Tight/balanced/loosening signal for macro agents and portfolio managers. Live source. Returns HTTP 503 (no charge) if upstream source unavailable for >50% of fields. | x402 SLA: $0.10 USDC per call. Returns HTTP 503 (no charge) when upstream data sources unavailable. data_source field discloses provenance (fred_api/fred_csv/fred_mixed).

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_labor_market_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
focusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover read-only/non-destructive/open-world, and the description adds real value beyond them: pricing ($0.10 USDC per call via x402), the failure mode (HTTP 503 with no charge when upstream is unavailable for >50% of fields), and the presence of a data_source provenance field (fred_api/fred_csv/fred_mixed). The only weakness is the 503/no-charge clause being stated twice in slightly different wording, which reads as patchwork rather than deliberate disclosure.

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 metric list is front-loaded and earns its place, but the tail is redundant: the HTTP 503/no-charge behavior appears twice in near-identical phrasing, and the piped 'x402 SLA' formatting mixes commerce terms with reliability terms. Trimming the duplicate would make it materially tighter.

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 output schema, the description carries the burden of describing returns; it discloses the signal trichotomy and the data_source provenance field but not the response shape or whether metrics come back as raw series, deltas, or indexed values. Failure and pricing semantics are well covered, so the gap is moderate rather than severe.

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 0% and the single `focus` parameter is never mentioned in the description, so an agent learns nothing about what focus filters or what the default is. The enum values (employment/wages/openings/all) are largely self-explanatory, which keeps this from being worse than baseline, but the description does not compensate for the coverage gap.

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?

Names a specific verb+resource (live labor market benchmarks) and enumerates the exact series covered: unemployment, U-6, JOLTS openings, quit rate, participation, weekly claims, wage growth. That is far more concrete than a sibling like get_macro_market_signal. It stops short of explicitly contrasting itself with those macro/broad-signal siblings, so it is clear but not fully differentiated.

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?

Says the output is a 'tight/balanced/loosening signal for macro agents and portfolio managers', which implies a use case but never states when to pick this over get_macro_market_signal or get_dol_labor_violations. No exclusions, prerequisites, or fallback guidance are given.

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