Skip to main content
Glama

labor-brief

Synthesize a US labor market briefing from 7 FRED signals using AI, providing labor regime, wage pressure, claims trends, Fed posture, and risk analysis for wage inflation and recession forecasting.

Instructions

AI-synthesized US labor market briefing. Fetches 7 FRED signals (initial claims, continued claims, JOLTS openings, nonfarm payrolls MoM, unemployment rate, wage growth YoY, labor force participation) and uses GPT-4o-mini to produce labor regime, wage pressure, claims trend, Fed posture signal, 150-word narrative, dominant risk, and agent implication. One call collapses 7 FRED lookups + LLM synthesis for wage inflation models, recession probability, and Fed policy forecasting.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses that the tool fetches 7 FRED signals and uses GPT-4o-mini for synthesis, listing output components. However, it does not mention potential costs, rate limits, or side effects of using an LLM.

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 concise, with three sentences front-loading the purpose. The structure is clear, though the second sentence is somewhat long.

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

Completeness5/5

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

For a tool with zero parameters and no output schema, the description comprehensively covers what the tool does, what data it uses, and what outputs it produces. It is complete and leaves no obvious gaps.

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 has zero parameters, so baseline score is 4. The description adds no parameter information, which is acceptable since no parameters exist.

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 clearly states the tool's purpose as an 'AI-synthesized US labor market briefing' and lists the specific data sources (7 FRED signals) and output components (labor regime, wage pressure, etc.). It is a specific verb+resource description that distinguishes it from other tools.

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?

The description implies usage for labor market analysis and synthesis, but does not explicitly state when to use this tool over alternatives (e.g., labor-market, macro-brief). No exclusion criteria or prerequisites are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/thebrierfox/the-stall'

If you have feedback or need assistance with the MCP directory API, please join our Discord server