Skip to main content
Glama

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

B3.3/5.0
Behavior4/5

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

Beyond the readOnly/openWorld annotations, the description discloses real operational behavior: an HTTP 503 with no charge when upstream sources fail for >50% of fields, a $0.10 USDC x402 charge per call, and a data_source provenance field (fred_api/fred_csv/fred_mixed). That is meaningful cost and failure-mode context an agent cannot get from annotations. It loses a point because the 503 policy is stated twice and the failure behavior is repeated rather than extended (no partial-result semantics).

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 useful, but the text is padded with near-duplicate statements: 'Live source.' plus the repeated HTTP 503 no-charge sentence, and the pipe-delimited x402 clause reads like billing boilerplate spliced into the description. Roughly a third of the content could be removed with no loss.

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 return-value burden; it does name the signal classification and the data_source provenance field, which helps. But it omits what the response actually looks like (metric values, units, time window/recency) and says nothing about the one input parameter, leaving gaps for a single-parameter benchmark tool.

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

Parameters2/5

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

Schema description coverage is 0% and the description never mentions the single 'focus' parameter at all, so the enum values (employment/wages/openings/all) have to speak for themselves. It is unclear whether omitting 'focus' defaults to 'all' or how the selection changes the returned fields — the description should compensate here and does not.

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 verb+resource ('Live labor market benchmarks from FRED') and enumerates the exact metrics covered (unemployment, U-6, JOLTS openings, quit rate, participation, claims, wage growth). That is enough to separate it from mortgage/rental/commodity benchmark siblings by subject matter, though no sibling is named explicitly.

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?

It states the output framing ('tight/balanced/loosening signal') and an intended audience ('macro agents and portfolio managers'), which implies when to reach for it. There is no explicit when-to-use vs. when-not guidance, no mention of the alternative macro-signal siblings, and no prerequisite/context requirements.

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