Skip to main content
Glama

LastLook Data

by io.github.zev-lll

Get Sahm Rule Recession Indicator

get_recession_indicator
Read-onlyIdempotent

Returns the real-time Sahm Rule recession indicator. A value >= 0.50 signals a recession is likely underway. Measures the rise in unemployment from its recent low. Source: FRED SAHMREALTIME.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
as_ofYesDate of the most recent observation
valueYesSahm Rule indicator value
signalYesHuman-readable signal description
thresholdYesTrigger threshold (0.50)
triggeredYesTrue if value >= 0.50 (recession signal active)

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already establish the tool as read-only and idempotent. The description adds valuable behavioral context: it defines the indicator as 'the rise in unemployment from its recent low,' specifies the 0.50 recession threshold, and cites the FRED SAHMREALTIME source. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three short sentences, each delivering specific content: what the tool returns, how to interpret the value, and the data source. There is no filler or redundancy.

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 zero-parameter read-only tool with an output schema, the description is sufficient. It states the output, the interpretation threshold, and the source, with no missing prerequisites or edge cases.

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 has zero parameters, and the schema confirms this with an empty properties object. The description does not need to explain input semantics, and it adds no param-specific information because none exists. Baseline 4 is appropriate.

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 opens with a specific action and resource: 'Returns the real-time Sahm Rule recession indicator.' It also clearly states the interpretation threshold and source, which distinguishes it from sibling getters like get_series or get_current_value.

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?

The description provides clear context for when to use this tool—to obtain the Sahm Rule indicator and check the recession threshold. It does not explicitly name alternatives or exclusions, but the tool's narrow scope makes its intended use obvious.

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

All LastLook Data toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation3/5

The tool set has several overlapping functions, particularly among the bundle tools (e.g., get_bundle_context_brief vs get_bundle_macro both provide macro indicators, and get_bundle_rate_environment overlaps with get_yield_curve and get_policy_spread). Individual current/history/date tools are distinct but some redundancy exists (e.g., get_treasury_yield_current vs get_current_value for DGS30). Descriptions help differentiate purposes, but agents may still hesitate when selecting between similar bundles.

Naming Consistency4/5

All tool names begin with the verb 'get_' and use snake_case, creating a consistent pattern. The bundle tools are uniformly prefixed with 'get_bundle_', and individual data tools follow a get_[entity]_[modifier] structure (e.g., get_fx_rate_current, get_fx_rate_by_date, get_fx_rate_series). Minor deviations exist (e.g., get_series, get_current_value, get_value_by_date are less descriptive of the underlying entity), but overall the naming is predictable and readable.

Tool Count3/5

With 24 tools, the server is on the heavy side of the typical range. The broad domain (macro data, mortgage, crypto, FX, treasury, EDGAR) justifies many tools, but some could potentially be consolidated (e.g., individual rate tools vs rate bundles). The count does not feel overwhelming, but it is borderline heavy.

Completeness4/5

The server covers a wide range of economic and financial data with both bundled and granular views. It includes current, historical, and date-specific retrievals for FRED series, FX, and crypto, plus specialized tools for mortgages, recession, and yield curves. Minor gaps exist, such as no way to list all supported FRED series or full financial statements for EDGAR, but the core lifecycle of data querying is well covered.

Resources