Skip to main content
Glama

Cash For My Note Calculators

Current 30-year mortgage rate and 10-year Treasury yield

market_rates
Read-onlyIdempotent

The current 30-year fixed mortgage rate here is the latest weekly Freddie Mac PMMS average, returned with the latest daily 10-year Treasury yield, each as a single value with its own data date, source and citation. History is not included; use the source links. Estimates, not offers or appraisals. CashForMyNote.com does not buy notes or make offers.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "market_rates"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds freshness semantics the annotations cannot express: one value is a weekly average, the other a daily yield, each stamped with its own date, source, and citation. That is real value beyond the structured fields.

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?

The core behavior is front-loaded in the first sentence, and the history limitation follows immediately. The trailing sentences are legal boilerplate ('Estimates, not offers or appraisals... does not buy notes or make offers') that slightly dilute an otherwise tight definition, though they do set expectations about the numbers.

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?

With no output schema, the description carries the burden of explaining return values, and it does: two single values, each with date, source, and citation. Combined with the explicit exclusion of historical data, an agent has enough to call and interpret it, though it does not say what happens if a source is stale or unavailable.

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 and the schema is fully closed, so the baseline of 4 applies. The description correctly implies no filtering or input options are needed.

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 resource pair with named sources: the latest weekly Freddie Mac PMMS 30-year fixed rate plus the latest daily 10-year Treasury yield. That is precise enough for an agent to know exactly what comes back. It does not differentiate itself from siblings such as rate_vs_market, which is the only gap.

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?

It gives a clear negative constraint ('History is not included; use the source links') and implicitly frames this as a point-in-time snapshot. It never says when an agent should prefer this over rate_vs_market or note_yield, so the choice among siblings 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.