Skip to main content
Glama

LastLook Data

by io.github.zev-lll

Get Mortgage Market Pulse Bundle

get_bundle_mortgage_pulse
Read-onlyIdempotent

Returns a complete mortgage market snapshot: 30yr and 15yr mortgage rates, 10Y Treasury yield, Fed funds rate, median home price (MSPUS), housing starts (HOUST), MBS spread (30yr mortgage minus 10Y), and 30-day rate trend signal. Use this for mortgage market analysis.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
as_ofYesDate of the most recent underlying data
bundleYesBundle identifier
seriesYesCurrent values for each series
derivedYesMBS spread and related computed fields
signalsYesRate trend signal

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, fully covering the safety profile. The description adds the bundled field list and the derived 30-day rate trend signal, which is useful output context, but it does not disclose operational details such as data freshness, units, or data source behavior beyond the series codes.

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 exactly two sentences: the first front-loads the action and lists all key data points compactly, and the second gives a single clear use case. No wasted or redundant words.

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 no-parameter, read-only bundle tool with a rich output schema and strong annotations, the description fully covers what the tool returns and when to use it. Including specific FRED series codes (MSPUS, HOUST) adds precision. With an output schema present, return-value details are not required.

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 is an empty object with 0 parameters, and schema description coverage is 100% vacuously. Per the rubric, 0 params yields a baseline score of 4. The description doesn't need to add parameter information, and it doesn't.

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 starts with 'Returns a complete mortgage market snapshot' and then enumerates the specific metrics included (30yr/15yr rates, 10Y Treasury, Fed funds, MSPUS, HOUST, MBS spread, trend signal). This clearly defines the tool's purpose and distinguishes it from sibling bundle tools like get_bundle_crypto or get_bundle_energy.

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 ends with 'Use this for mortgage market analysis,' providing a clear context for when to use it. It doesn't explicitly mention alternatives or when not to use it, but the mortgage-specific scope and the list of other bundle tools in the sibling context imply differentiation.

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