Skip to main content
Glama

LastLook Data

by io.github.zev-lll

Get Refinance Signal Bundle

get_bundle_refi_signal
Read-onlyIdempotent

Returns a refinance signal bundle: current 30yr and 15yr mortgage rates, 52-week high/low range, MBS spread over 10Y Treasury, 30-day and 90-day rate trend, and a refi break-even threshold. The refi_breakeven_threshold field directly answers "what rate does a borrower need to have to benefit from refinancing today?" Priced at $0.60 USDC via x402 on Base.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
as_ofYesDate of the most recent underlying data
bundleYesBundle identifier: refi_signal
seriesYesMORTGAGE30US, MORTGAGE15US, DGS10, FEDFUNDS
derivedYesmbs_spread, week52_high, week52_low, week52_position_pct, refi_breakeven_threshold
signalsYesrate_trend_30d, rate_trend_90d, rate_vs_52wk, refi_environment

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the description doesn't repeat those. It adds the pricing detail ($0.60 USDC via x402 on Base) and clarifies the meaning of the breakeven field, which is beyond the annotations and useful for an agent considering invocation.

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?

Three sentences, front-loaded with the core result, lists contents efficiently, explains one key field, and provides pricing. No wasted 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?

An output schema exists, so return values are already structured. The description adds field meaning and pricing, making it complete for a no-parameter tool with a good annotation set.

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 accepts zero parameters, so the description carries no parameter burden. Baseline of 4 applies; the description doesn't need to explain inputs.

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 clearly states it returns a refinance signal bundle and enumerates its components (mortgage rates, 52-week range, MBS spread, trends, breakeven threshold). While it doesn't explicitly contrast with sibling bundles, the name and listing of specific refi data make the purpose unambiguous.

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 implies use for refinancing decisions, especially by explaining that the breakeven threshold directly answers what rate a borrower needs to benefit. It doesn't provide exclusions or alternatives, but the context is clear.

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