Skip to main content
Glama

Haven Financing

Compare with existing debt

compare_existing_debt
Read-onlyIdempotent

Compares an existing loan (margin, SBLOC, HELOC, mortgage, personal loan, credit card) with Haven's all-in cost on every term: annual cost, savings, the lowest-cost option and the collateral Haven would need.

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": {
      "balance": "<balance>",
      "currentRatePercent": "<currentRatePercent>"
    },
    "name": "compare_existing_debt"
  }
}

Input Schema

NameRequiredDescriptionDefault
balanceYesOutstanding balance of the existing loan, in USD.
debtTypeNoKind of existing debt: margin, sbloc, heloc, mortgage, personal_loan, credit_card or other.
collateralValueNoMarket value of the brokerage portfolio that would secure Haven financing, in USD.
currentRatePercentYesThe existing loan's annual interest rate, in percent (e.g. 8.25).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description earns credit by disclosing the computations returned (annual cost, savings, lowest-cost option, required collateral), which is valuable since there is no output schema to convey return shape.

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?

A single front-loaded sentence with no filler; the comparison subject comes first, followed by the enumerated outputs. The parenthetical debt list is mildly redundant with the enum but still scannable and purposeful.

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 4-parameter, fully documented, read-only calculation with no output schema, the definition covers purpose and return contents adequately. It stops short of explaining whether collateralValue is mandatory for certain debt types or how missing collateral is handled, a minor gap.

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%, so every parameter is already documented in the schema and the baseline is 3. The parenthetical debt list merely mirrors the debtType enum, and the description adds no syntax or interaction detail for balance, currentRatePercent or collateralValue.

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 ("Compares") and resource (an existing loan vs. Haven's all-in cost), and enumerates the concrete debt kinds covered. It implicitly separates itself from simulate_financing by framing the input as an existing loan, but never names the sibling, so the differentiation is inferred rather than stated.

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 comparison framing implies the situation (a prospect already holding a loan who wants a side-by-side against Haven), but there is no explicit when-to-use trigger, no when-not condition, and no named alternative such as simulate_financing or get_current_rates. The agent must infer the routing decision.

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