Skip to main content
Glama

Haven Financing

Simulate portfolio financing

simulate_financing
Read-onlyIdempotent

Calculate indicative financing costs for users considering borrowing against an investment portfolio. Accept portfolio value, requested financing amount, and selected term. When users have authorized access to connected financial information, relevant portfolio values and existing borrowing details may be used as calculation inputs, subject to applicable permissions and user consent. Return current Haven rates, advisory fees, estimated financing costs, loan-to-value ratios, and applicable eligibility and collateral risk disclosures. Do not request account credentials or unnecessarily detailed personal holdings.

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": {
      "collateralValue": "<collateralValue>",
      "drawAmount": "<drawAmount>"
    },
    "name": "simulate_financing"
  }
}

Input Schema

NameRequiredDescriptionDefault
termNoFixed-rate term: 3M, 6M, 12M (or 1Y) or 2Y. Ignored for variable financing.
rateTypeNofixed: rate set for the term at execution. variable: resets monthly at the 1M rate.
drawAmountYesCash to borrow, in USD. Minimum $50,000.
collateralValueYesMarket value of the eligible brokerage portfolio pledged as collateral, in USD.
existingHavenBalanceNoHaven financing already outstanding against the same collateral, in USD. Default 0.
comparisonRatePercentNoAnnual rate to compare against, in percent (default 7.5, an approximate brokerage margin rate).

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, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds meaningful context: conditional use of connected financial data subject to permissions and consent, and a privacy constraint against requesting credentials or detailed holdings. What it omits is any statement about precision, caching, or that results are non-binding estimates only (it says 'indicative', which partly covers this).

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?

Front-loaded with purpose, then inputs, then conditional data-access behavior, then outputs. The consent/permissions sentence is somewhat hedged and wordy ('subject to applicable permissions and user consent'), but no sentence is entirely 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?

With no output schema, the description carries the burden of describing returns and does so: rates, advisory fees, estimated costs, LTV ratios, and eligibility/collateral risk disclosures. Combined with 100% schema coverage on the six inputs, an agent has enough to invoke correctly; only the missing sibling routing keeps it below full marks.

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%, so every parameter is already documented in detail, including enums for term and rateType. The description names only three of the six inputs (portfolio value, financing amount, term) and adds nothing about existingHavenBalance, comparisonRatePercent, or how term is ignored for variable financing. Baseline 3 is appropriate.

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: 'Calculate indicative financing costs' for borrowing against an investment portfolio. The simulation framing distinguishes it from a live-rate lookup like get_current_rates, but the description never names or contrasts a sibling 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?

The target scenario ('users considering borrowing against an investment portfolio') is stated, which implies when to call it. However, there is no guidance on when NOT to use it, and no routing to compare_existing_debt or get_current_rates even though the tool returns rates and debt-adjacent figures.

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