Skip to main content
Glama

Mortgage Rates

rates_mortgage
Read-onlyIdempotent

National mortgage rate series. (Source: BankRegReports.)

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": "rates_mortgage"
  }
}

Input Schema

NameRequiredDescriptionDefault
productNoMortgage product, e.g. 30yr_fixed or 15yr_fixed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered structurally. The description adds only a source attribution (BankRegReports) and says nothing about default behavior when 'product' is omitted, rate periods covered, or freshness of the series.

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?

Two short sentences with no filler and the resource named up front. It is not padded, though the parenthetical source note is the only content beyond the noun phrase, so brevity here reflects thinness more than discipline.

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

Completeness2/5

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

There is no output schema and the description never indicates what a result looks like (a current rate, a time series, a single value), nor the default when 'product' is absent. For a simple one-parameter read tool this is a meaningful gap that leaves the agent unable to predict the response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With a single parameter and 100% schema description coverage, the schema already documents that 'product' accepts values like 30yr_fixed or 15yr_fixed. The description adds no additional meaning, such as whether the parameter is optional in practice or what happens when it is omitted, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource as a 'national mortgage rate series' with a source attribution, which is clearer than the bare title, but it contains no verb and never distinguishes this tool from siblings such as rates_national, rates_consumer, or mortgage_performance. An agent knows roughly what data domain it touches but not exactly what the call returns or does.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of alternatives, and no exclusions. The description does not say how this differs from the other rate series tools in the sibling list, leaving the agent to guess based on the name alone.

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.

Resources