Skip to main content
Glama

Haven Financing

Search Haven reference documents

search
Read-onlyIdempotent

Searches Haven's reference documents (current rates, fees, collateral limits, rate locks, savings method, risks). Returns ids to pass to fetch.

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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesWhat to look for, e.g. 'advisory fee' or 'loan to value'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world). The description adds one genuinely useful behavioral fact: results are ids, not document text, so a follow-up fetch is required. It says nothing about ranking, result limits, or how many hits to expect, which the annotations cannot supply.

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?

Two short sentences with zero waste; the core action and the id-to-fetch handoff are both front-loaded. Nothing here is redundant filler.

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 one-parameter read-only lookup with a fully described schema and complete annotations, this covers what an agent needs to call it and chain it into fetch. The only real omission is disambiguation against sibling tools that cover overlapping rate information.

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% and the single query parameter already documents its purpose with examples ('advisory fee', 'loan to value'). The description's list of domains gives loose topical hints but adds no syntax, matching behavior, or phrasing guidance beyond the schema baseline.

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 (Searches) and resource (Haven's reference documents), then enumerates the content domains covered: rates, fees, collateral limits, rate locks, savings method, risks. It also implicitly separates itself from the sibling 'fetch' by noting it returns ids rather than content. It stops short of naming the real ambiguity, which is search vs. get_current_rates on rate queries.

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 implied via the two-step workflow: search to get ids, then pass them to fetch. There is no explicit when-not guidance, and the listed domain 'current rates' overlaps with the sibling get_current_rates, so an agent still has to guess which tool to pick for rate questions.

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