Skip to main content
Glama

FreeRateUpdate Mortgage & Home Equity Shopping

Published mortgage and home equity answers

get_content_answer
Read-onlyIdempotent

A published FreeRateUpdate answer to a mortgage or home-equity question, pinned to the edition it was published in. Ask by exact slug, or by keywords that are matched against the title and slug. Topics covered include HELOC and home equity, purchase, refinance and cash-out, FHA and VA, reverse mortgage, and DSCR and investment property. Only published answers are returned.

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_content_answer"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoExact public URL slug
queryNoKeyword search over title/slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description usefully adds that results are restricted to published answers and versioned to a specific edition, but says nothing about result count, pagination, or what happens on a slug miss.

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?

Four tight sentences, front-loaded with the resource definition before the query modes and topic coverage. The topic enumeration is somewhat long but earns its place by telling the agent which keywords will actually hit content.

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 two-optional-parameter read tool with no output schema, the description covers what is returned at a conceptual level (a published answer, tied to its edition) and the published-only constraint. Missing only minor operational detail such as behavior when neither parameter is supplied or when no match exists.

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?

Schema coverage is 100% and already documents both fields as "Exact public URL slug" and "Keyword search over title/slug," which the description essentially restates. The one small addition is framing them as alternatives (slug OR keywords), but no format, precedence, or combination behavior is clarified beyond the schema.

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?

"A published FreeRateUpdate answer to a mortgage or home-equity question" names the exact resource and its scope, and the topic list (HELOC, refinance, FHA/VA, DSCR) makes clear this is editorial Q&A content rather than rates or lender data. The retrieval verb is only implied by "Ask by exact slug, or by keywords," so it is clear but not stated crisply.

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 explains the two ways to invoke it (exact slug vs. keyword match on title/slug) and that only published answers come back, which implies usage context. It never states when to prefer this over a sibling numeric tool or what to do if no answer matches, so guidance is implied rather than explicit.

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