Skip to main content
Glama

FreeRateUpdate Mortgage & Home Equity Shopping

FreeRateUpdate Score for a lender

get_lender_score
Read-onlyIdempotent

The FreeRateUpdate Score (0-100) for a verified, currently in-network lender by company NMLS id, with factor breakdown and methodology link. Companies without a published current Score are not found.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "nmls": "<nmls>"
    },
    "name": "get_lender_score"
  }
}

Input Schema

NameRequiredDescriptionDefault
nmlsYesCompany NMLS id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds useful non-annotation context: the 0-100 range, the in-network verification requirement, the factor breakdown/methodology payload, and the not-found behavior for unscored companies. It doesn't describe response shape or staleness/refresh cadence of the score, keeping this at a 3.

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?

One dense sentence plus a short caveat sentence; scope, return contents, and the not-found condition are front-loaded. Slightly packed with parenthetical detail but nothing is wasted.

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 single-parameter read tool with no output schema, the description covers the identifier, the return payload, and the failure mode. Minor gaps remain around how the breakdown is structured and whether the score is cached, but the essentials for correct invocation are present.

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 the single nmls parameter is already documented with a pattern. The description reinforces that nmls means 'company NMLS id' for a lender, adding modest semantic context (company-level, not individual) but no format or edge-case guidance beyond the schema.

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+resource (returns the FreeRateUpdate Score 0-100 for a lender) plus the keying identifier (company NMLS id) and the payload (factor breakdown, methodology link). This clearly distinguishes it from siblings like get_lender_profile or get_lender_figures, which lack the score concept.

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?

The description implies when the tool applies by scoping it to 'verified, currently in-network lender' and noting that companies without a published current Score are not found. It does not explicitly route the agent away from get_lender_figures or get_lender_profile, so usage is implied rather than contrasted.

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