Skip to main content
Glama

BRAINIAC Consumer Credit & Deposit Disclosures

HPA PMI termination dates

consumer-credit_pmi-termination-dates
Read-onlyIdempotent

Compute Homeowners Protection Act cancellation, automatic termination and final termination dates from the amortization schedule. Price $0.03 USDC. POST /api/v1/consumer-credit/pmi-termination-dates. An unpaid call returns the x402 payment terms and does not run.

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": {
      "loanAmount": "<loanAmount>",
      "annualRate": "<annualRate>",
      "termMonths": "<termMonths>",
      "firstPaymentDate": "<firstPaymentDate>",
      "appraisedValue": "<appraisedValue>",
      "purpose": "<purpose>"
    },
    "name": "consumer-credit_pmi-termination-dates"
  }
}

Input Schema

NameRequiredDescriptionDefault
purposeYespurpose, string, one of purchase, refinance. Required.
annualRateYesannualRate, number, from 0 to 1. Required.
loanAmountYesloanAmount, integer, from 1 to 9007199254740991. Required.
salesPriceNosalesPrice, integer, from 1 to 9007199254740991. Optional.
termMonthsYestermMonths, integer, from 12 to 600. Required.
appraisedValueYesloanAmount, integer, from 1 to 9007199254740991. Required.
monthlyPaymentNomonthlyPayment, value. Optional.
currentScheduleNocurrentSchedule, array. Optional.
firstPaymentDateYesfirstPaymentDate, string. Required.

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
limitationsNolimitations. Array.
originalValueNooriginalValue. Number.
monthlyPaymentNomonthlyPayment. Number.
terminationDateNoterminationDate. String.
cancellationDateNocancellationDate. String.
finalTerminationDateNofinalTerminationDate. String.
midpointPaymentNumberNomidpointPaymentNumber. Number.
terminationPaymentNumberNoterminationPaymentNumber. Number.
cancellationPaymentNumberNocancellationPaymentNumber. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds genuinely non-structured behavior: a fixed $0.03 USDC price and the x402 payment handshake on unpaid calls, which an agent must know before invoking. It does not describe error cases or output shape, but an output schema exists to cover the latter.

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?

Three short sentences, front-loaded with the computation, followed by price and endpoint, then the payment-behavior caveat. No filler and no repetition of schema 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 nine-parameter, one-endpoint computation tool with a rich annotation set and an output schema, the description covers purpose, cost, transport, and payment behavior adequately. The remaining gap is that it never explains what omitting currentSchedule or monthlyPayment does to the calculation, which matters for a tool whose optional inputs change the derivation path.

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 100% and six of nine parameters are required, so the schema carries the parameter burden. The description adds only the framing that the calculation derives from an amortization schedule, hinting at the optional currentSchedule input, without explaining its format or its effect on results. Baseline 3 is appropriate.

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 ('Compute') and a specific regulatory output set (HPA cancellation, automatic termination, and final termination dates) plus the input source (amortization schedule). That is clearly distinguishable from the siblings, which cover APY, Reg F, Reg Z APR, and UK early settlement, none of which compute HPA PMI dates.

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 through 'from the amortization schedule'; there is no explicit statement of when to prefer this tool or when it does not apply (e.g. non-HPA loans, FHA/VA cases). The payment-gating note is helpful context but is not selection guidance.

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