Skip to main content
Glama

bluerate: Find a Mortgage Loan Officer

Get a loan officer's profile

get_loan_officer
Read-onlyIdempotent

Returns one loan officer's bluerate.ai profile by NMLS ID: name, company, licensed states, loan types, languages, about text, up to 3 client reviews, FAQs and url: the loan officer's public bluerate profile, where people request a callback. Contains no phone numbers or email addresses.

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

Input Schema

NameRequiredDescriptionDefault
nmlsYesThe loan officer's NMLS ID, digits only, for example 123456: the nmls field of a search result.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / nmls / description
      Previous value: -"The loan officer's NMLS ID, digits only, for example 123456. search_loan_officers returns it as nmls."New value: +"The loan officer's NMLS ID, digits only, for example 123456: the nmls field of a search result."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world behavior, and the description adds genuine value on top: the exact field set returned, a bounded 'up to 3 client reviews', and the negative disclosure that no phone numbers or email addresses are present. It doesn't mention error behavior for an invalid or unknown NMLS ID, which keeps it from a 5.

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?

One dense, front-loaded sentence: verb+resource+key first, then the payload list, then the useful exclusion. No filler or repeated information.

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

Completeness5/5

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

No output schema exists, so the description carries the full burden of describing return values, and it does so field by field, including the callback URL and the absence of contact details. For a one-parameter read tool with full annotation coverage, nothing an agent needs in order to call it correctly is missing.

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?

There is a single parameter with 100% schema description coverage, and the schema already explains the digits-only format and the example. The description's 'by NMLS ID' adds no format or syntax detail beyond what the schema provides, so the baseline of 3 applies.

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?

States a specific verb and resource ('Returns one loan officer's bluerate.ai profile') plus the lookup key (NMLS ID) and enumerates the returned fields. The singular 'one ... profile by NMLS ID' implicitly contrasts with search_loan_officers, but no sibling is named explicitly.

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?

No explicit when-to-use or when-not-to-use statement, and request_callback is never mentioned even though the description references the callback URL. Usage is only implied by the phrase 'one loan officer's profile by NMLS ID', which suggests a follow-up to a search lookup.

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