Skip to main content
Glama

FHA, VA or USDA loan fees

government_loan_fees
Read-onlyIdempotent

The published government fee a program adds to an anonymized loan: FHA upfront and annual mortgage insurance premium (MIP) and how long it runs, the VA funding fee, or the USDA guarantee fee, from the agency schedules with their effective dates. A published fee, never an interest rate and never a credit decision.

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": {
      "program": "<program>",
      "loan_amount": "<loan_amount>",
      "ltv": "<ltv>"
    },
    "name": "government_loan_fees"
  }
}

Input Schema

NameRequiredDescriptionDefault
ltvYesloan-to-value, e.g. "96.5" or "100%", at most two decimals
programYes
va_exemptNoVA only: a borrower exempt from the funding fee
term_yearsNoloan term in years; required for FHA
va_purposeNoVA only
loan_amountYesbase loan amount, e.g. "$300,000"
va_first_useNoVA only: first use (default true)

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?

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine context beyond that: fees come from published agency schedules with effective dates, and the loan is anonymized so no borrower PII is required. It still says nothing about determinism across schedule updates, rounding behavior, or how results vary with the conditional VA/FHA parameters.

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 sentences, front-loaded with the resource and its program-specific fee types, then closed with a scope exclusion that genuinely earns its place by preventing misuse as a pricing or underwriting tool. Wording is dense and clause-heavy ('FHA upfront and annual mortgage insurance premium (MIP) and how long it runs') but contains no filler.

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 7-parameter, read-only, no-output-schema tool, the description covers domain, data provenance, effective dates, and output shape well enough to call it correctly. The remaining gap is conditional-parameter behavior, which the schema descriptions largely absorb, so the omission is not material.

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 description coverage is 86%, so the schema already documents loan_amount, ltv, term_years, va_purpose, va_first_use and va_exempt; baseline is 3. The description adds only indirect meaning — 'how long it runs' hints that term_years drives MIP duration — and never explains the conditional structure (VA-only fields, term_years required for FHA) that an agent could otherwise trip on.

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?

The description names the exact resource returned per program — FHA upfront and annual MIP (plus duration), the VA funding fee, and the USDA guarantee fee — sourced from agency schedules with effective dates. That is far more specific than the bare name 'government_loan_fees'. It stops short of naming sibling tools (llpa_cost, loan_limit) to route against, though the 'never an interest rate and never a credit decision' line implicitly fences off pricing and eligibility siblings.

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?

Usage is only implied: an agent can infer this is for computing statutory program fees on a hypothetical loan scenario, and the closing sentence rules out rate quoting and credit decisions. There is no explicit when-to-use statement, no named alternative for pricing questions (e.g. llpa_cost), and no stated prerequisites or preconditions for a valid call.

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