Market Eyes Live - stock ratings and mortgage-rate context

Get mortgage rate context

get_mortgage_rate_context

Read-onlyIdempotent

Returns today's public U.S. mortgage-rate context from Market Eyes Live: the 10-year Treasury yield and its direction, mortgage-backed securities (MBS) momentum, the overall rate environment (falling, stable or rising), and a short explanation of what moves mortgage rates. Use this when the user asks what is driving U.S. mortgage rates or which way the rate environment is moving, for example 'what is driving mortgage rates this week' or 'are mortgage rates rising or falling'. Do not use for a specific lender's quoted rate, APR or fee comparisons, loan qualification, a personal lock decision, or anything outside the United States. Limitations: a daily read built from public market data; it describes conditions and does not forecast any individual's rate. Public market data and general education, not financial advice; this tool is read-only.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`mbs`	No
`as_of`	No	YYYY-MM-DD of the data
`links`	No
`source`	Yes
`disclaimer`	Yes
`rate_environment`	No	falling, stable, or rising
`ten_year_treasury`	No
`what_moves_mortgage_rates`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 7, 2026
- addedOutput schema / properties / disclaimer
```
Added value: +{
+  "type": "string"
+}
```
- removedOutput schema / properties / links / properties / app
```
Removed value: -{
-  "type": "string"
-}
```
- addedOutput schema / properties / links / properties / lock_or_float_explainer
```
Added value: +{
+  "type": "string"
+}
```
- removedOutput schema / properties / links / properties / should_i_lock
```
Removed value: -{
-  "type": "string"
-}
```
- addedOutput schema / properties / source
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / required
```
Added value: +[
+  "source",
+  "disclaimer"
+]
```

Changed1 schema field changedAug 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "today's public mortgage-rate context; omitted only if the live feed is momentarily unavailable, which returns a text message instead",
+  "properties": {
+    "as_of": {
+      "description": "YYYY-MM-DD of the data",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "links": {
+      "properties": {
+        "app": {
+          "type": "string"
+        },
+        "live_data": {
+          "type": "string"
+        },
+        "should_i_lock": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "mbs": {
+      "properties": {
+        "meaning": {
+          "type": "string"
+        },
+        "momentum": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "rate_environment": {
+      "description": "falling, stable, or rising",
+      "type": "string"
+    },
+    "ten_year_treasury": {
+      "properties": {
+        "direction": {
+          "type": "string"
+        },
+        "yield_pct": {
+          "type": [
+            "number",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "what_moves_mortgage_rates": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedJul 17, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: it is a daily read sourced from public market data, it describes conditions without forecasting any individual's rate, and it is education rather than financial advice.

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?

Front-loaded with the returned data, then usage, then exclusions, then limitations – a logical order with no wasted sentences. It runs slightly long because of the compliance-flavored disclaimers, but those carry real behavioral meaning rather than filler.

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-value documentation is not needed, and with no parameters the schema side is trivially complete. Scope, exclusions, data freshness and the non-forecast/advice boundaries together give an agent everything required to call it correctly.

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 takes zero parameters, so the baseline is 4 and there is nothing for the description to compensate for. It appropriately avoids inventing or describing inputs that do not 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?

States a specific verb and resource plus the exact payload: 10-year Treasury yield and direction, MBS momentum, the rate environment (falling/stable/rising), and a short explanatory note. That level of detail makes it unmistakable against the stock-focused siblings compare_stocks and get_stock_rating.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives both positive triggers with concrete example prompts ('what is driving mortgage rates this week', 'are mortgage rates rising or falling') and an explicit negative list (lender quotes, APR/fee comparisons, qualification, personal lock decisions, non-US markets). Nothing is left to inference.

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

All Market Eyes Live - stock ratings and mortgage-rate context tools Inspect

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.