Skip to main content
Glama

Haven Financing

Create a prefilled onboarding link

create_onboarding_link
Read-onlyIdempotent

Builds a link that opens Haven's financing simulator prefilled with a scenario, where the investor can review it and apply. Creates nothing and submits nothing; the link carries no personal data.

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": "create_onboarding_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
termNoFixed-rate term: 3M, 6M, 12M (or 1Y) or 2Y. Ignored for variable financing.
sourceNoOptional short label for the client creating the link, e.g. chatgpt. Recorded as utm_source.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnly, non-destructive, idempotent and closed-world. The description earns credit by adding behavior annotations cannot convey: no record is created, nothing is submitted, and the link embeds no personal data — direct answers to the privacy and side-effect questions an agent would have. It omits link lifetime/expiry and whether links can be revoked.

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 short clauses: the positive purpose first, then the negative guarantees. Front-loaded and free of filler, though the semicolon-joined caveats read as a list rather than a structured guidance section.

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?

No output schema exists, so one could ask what the tool returns (a URL string, an object with metadata?), which the description only implies with 'Builds a link'. Otherwise it is complete for a five-parameter, non-mutating tool whose schema is fully documented.

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%, with enums and units documented inline, so the baseline is 3. The description names only 'a scenario' generically and adds no meaning about collateralValue, drawAmount, rateType, term, or source beyond the schema.

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?

Names a specific verb and resource ('Builds a link that opens Haven's financing simulator prefilled with a scenario'), which is far more specific than the title alone. It does not, however, distinguish itself from plausible siblings like simulate_financing, which the reader must infer is a different (non-link) path.

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 phrase 'where the investor can review it and apply' implies the use case (handing a scenario to an external investor), but there is no explicit when-to-use or when-not-to-use statement and no named alternative. With siblings such as simulate_financing and get_current_rates present, routing guidance is left to inference.

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