Skip to main content
Glama

Haven Financing

Get current Haven rates

get_current_rates
Read-onlyIdempotent

Haven's current financing rates for each fixed term (3M, 6M, 1Y, 2Y) and the monthly variable rate: financing rate, Haven fee, all-in rate, illustrative after-tax rate, as-of time and rate-lock eligibility.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_current_rates"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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 adds genuinely useful behavior beyond that: the returned field set (financing rate, Haven fee, all-in rate, after-tax illustrative rate), the presence of an as-of timestamp for freshness, and rate-lock eligibility. It stops short of saying whether rates are workspace-scoped or globally published.

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?

A single front-loaded sentence that opens with the resource and then lists the covered terms and fields. The parenthetical term list is dense but each element is substantive; nothing is redundant or padded.

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 parameters and no output schema, the description correctly carries the burden of describing return content, and it does so thoroughly, including the as-of time and rate-lock eligibility. Minor gap: it does not clarify whether the response is a single object keyed by term or a list, which matters given the absent output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4 and there is nothing for the description to disambiguate. It correctly avoids inventing parameter talk and instead spends its words on scope and output shape.

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 a specific resource (Haven's current financing rates) and enumerates the exact scope: fixed terms 3M/6M/1Y/2Y plus the monthly variable rate, with the fields returned. It does not explicitly contrast itself with simulate_financing or compare_existing_debt, so an agent must infer that this is a read of published rates rather than a per-scenario calculation.

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 — the wording makes it obvious this is a rate lookup, but there is no statement of when to call it versus simulate_financing (per-scenario projection) or compare_existing_debt. No prerequisites, no exclusions, and no mention of how rate-lock eligibility relates to a specific borrower.

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