Skip to main content
Glama
Sign In

LastLook Data

by io.github.zev-lll
OverviewDiscussionsAdmin

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?" Price: $0.60 USDC per call via x402 (Base or Solana).

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "as_of": {
-      "description": "Date of the most recent underlying data",
-      "type": "string"
-    },
-    "bundle": {
-      "description": "Bundle identifier: refi_signal",
-      "type": "string"
-    },
-    "derived": {
-      "additionalProperties": {},
-      "description": "mbs_spread, week52_high, week52_low, week52_position_pct, refi_breakeven_threshold",
-      "type": "object"
-    },
-    "series": {
-      "additionalProperties": {
-        "type": [
-          "number",
-          "null"
-        ]
-      },
-      "description": "MORTGAGE30US, MORTGAGE15US, DGS10, FEDFUNDS",
-      "type": "object"
-    },
-    "signals": {
-      "additionalProperties": {
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "description": "rate_trend_30d, rate_trend_90d, rate_vs_52wk, refi_environment",
-      "type": "object"
-    }
-  },
-  "required": [
-    "as_of",
-    "bundle",
-    "series",
-    "derived",
-    "signals"
-  ],
-  "type": "object"
-}New value: +null
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, openWorld, and non-destructive behavior, so the description does not need to repeat safety hints. It adds useful context by disclosing the $0.60 USDC per-call cost via x402 on Base or Solana and by explaining the practical meaning of the breakeven threshold field. It still omits freshness, source latency, and rate-limit details.

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 front-loads the returned bundle contents and uses compact sentences with no wasted preamble. The pricing note is appended cleanly and every sentence contributes useful information.

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

Completeness4/5

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

Because there is no output schema, the description appropriately enumerates the key return fields and defines the refi_breakeven_threshold. It is nearly complete for invocation, but it does not mention data freshness/source, output structure, or update cadence for an openWorld paid data bundle.

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, so the baseline is 4. The empty input schema has 100% description coverage, and no parameter semantics need to be explained in the description.

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 states a specific verb and resource: 'Returns a refinance signal bundle' and enumerates the contents, including 30yr/15yr rates, 52-week range, MBS spread, trends, and breakeven threshold. It is clear what the tool does, but it does not explicitly distinguish the bundle from siblings such as calc_refinance, get_bundle_mortgage_pulse, or get_bundle_rate_environment.

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 by saying the refi_breakeven_threshold field answers whether a borrower benefits from refinancing today. However, it gives no explicit when-to-use guidance, exclusions, or comparison against calc_refinance or the mortgage/rate bundle siblings.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources