Skip to main content
Glama

FreeRateUpdate Mortgage & Home Equity Shopping

Network advertised rate summary

get_network_rate_summary
Read-onlyIdempotent

Network-aggregate advertised-rate summary (min/avg APR + distinct-lender count per product bucket, min 5 lenders per bucket) from the latest fresh FreeRateUpdate rate snapshot. Aggregates only — no per-lender rates.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive behavior, so the description's added value is the data policy: a minimum of 5 lenders per bucket (suppression of thin buckets) and use of the latest fresh FreeRateUpdate snapshot rather than any snapshot. That is meaningful beyond the annotations, though it doesn't say what happens to suppressed buckets (omitted vs. null) or how freshness is bounded.

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?

Two sentences, no filler, with the returned measures and the lender-floor constraint front-loaded before the exclusion clause. Every phrase carries information an agent needs.

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?

For a zero-parameter, read-only tool with no output schema, the description supplies the key return fields and the suppression rule, which is enough to call it correctly. It leaves 'product bucket' undefined and doesn't quantify snapshot recency, minor gaps for an otherwise simple tool.

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 no parameters, so there is nothing for the description to disambiguate; baseline is 4. The description implicitly confirms the zero-input nature by describing a single fixed network-level aggregation.

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 resource (network-aggregate advertised-rate summary) and enumerates the returned measures: min/avg APR plus distinct-lender count per product bucket. The closing clause 'Aggregates only — no per-lender rates' clearly separates it from the per-lender siblings such as get_lender_figures or get_lender_profile.

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 phrase 'Aggregates only — no per-lender rates' gives a clear negative boundary that steers an agent away from lender-level tools, and 'latest fresh ... snapshot' signals when the data is appropriate. It stops short of naming an explicit alternative for per-lender detail or stating when the summary is insufficient (e.g. sparse buckets).

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