Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_boat_loan

Calculates boat loan monthly payments, required down payments, and total financing costs for new and used boats using price, rate, term, and down payment percentage.

Instructions

Boat Loan Financing & Payment Calculator. Calculate marine loan monthly payments, required down payments (10-20%), and total financing costs for new and used boats and yachts. Discipline: FINANCE. Governing mathematical model / formula: Financed Principal = Boat Price - Down Payment + Sales Tax.

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of boat_payment (Monthly Marine Payment), down_amt (Required Down Payment), total_boat_interest (Total Marine Interest) using boat_price (Boat Purchase Price), down_pct (Down Payment (%) in %), loan_rate (Interest Rate (%) in %), loan_term_yrs (Loan Term (Years) in yrs). Guarantees exact machine floating-point precision, eliminating LLM arithmetic mistakes and formula hallucinations.

  • WHEN NOT TO USE: Do not use for qualitative evaluations or unquantified reasoning. All input parameters must be valid numerical values.

DISAMBIGUATION & BOUNDARIES:

  • Use this dedicated specialist tool for 'Boat Loan Financing & Payment Calculator' rather than generic dispatchers like omni_universal_query.

  • For multi-calculation chained jobs, use 'omni_batch_calculate'.

  • To inspect schema fields, see 'omni_describe_solver'.

BEHAVIOR & SAFETY:

  • Pure deterministic computation with machine floating-point precision.

  • Read-only, idempotent, and stateless. Zero side effects or persistent state mutations.

  • Input validation: All arguments are validated against physical and domain bounds. Out-of-bounds inputs return a safe diagnostic error status without throwing runtime exceptions.

RETURNS:

  • Structured JSON object containing:

    • status (string): "success" on valid execution or "error" if validation fails

    • calculator (string): "boat-loan"

    • category (string): "finance"

    • name (string): "Boat Loan Financing & Payment Calculator"

    • formula (string): Governing mathematical formula string

    • inputs (object): Echoed input parameter dictionary with applied defaults

    • metrics (object): Dictionary of computed outputs:

      • metrics.boat_payment (Monthly Marine Payment): Formatted display string (e.g. '$528.40')

      • metrics.down_amt (Required Down Payment): Formatted display string (e.g. '$9,750.00')

      • metrics.total_boat_interest (Total Marine Interest): Formatted display string (e.g. '$39,862.00')

    • execution_time_ms (number): Latency in milliseconds.

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

Input Schema

NameRequiredDescriptionDefault
down_pctNoDown Payment (%) (%). 10-20% standard marine down payment. Default: 15. Min: 0. Max: 50.
loan_rateNoInterest Rate (%) (%). Annual marine APR. Default: 7.99. Min: 4. Max: 18.
boat_priceNoBoat Purchase Price. Agreed price of vessel. Default: 65000. Min: 5000. Max: 500000.
loan_term_yrsNoLoan Term (Years) (yrs). Marine loan durations typically 10 to 20 years. Default: 15. Min: 5. Max: 20.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden and does so well: it declares read-only, idempotent, stateless behavior with zero side effects, and explains that out-of-bounds inputs return a diagnostic error rather than throwing. It stops short of stating whether defaults are applied silently versus echoed, though the RETURNS section hints at 'applied defaults'.

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?

Well front-loaded with labeled sections (usage, disambiguation, behavior, returns) that make scanning easy. It is longer than strictly necessary, with some restatement between the opening sentence and the USAGE block, but no sentence is pure filler given the absence of an output schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations, the description compensates fully by documenting the return envelope (status, calculator, category, formula, inputs, metrics with formatted strings) and the safety profile. An agent has everything needed to call it and interpret the result.

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 defaults, min/max, and per-field explanations already in the schema, so the baseline is 3. The description restates the four parameter names and units but adds no syntax, interaction, or edge-case meaning beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Calculate marine loan monthly payments, required down payments... total financing costs') and scopes it to new and used boats and yachts. It also names the governing formula, so an agent can distinguish it from generic dispatchers and from sibling loan calculators like omni_bridge_loan_interest or omni_rv_loan.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit WHEN TO USE with the exact input/output names, an explicit WHEN NOT TO USE ('qualitative evaluations or unquantified reasoning'), and named alternatives: omni_universal_query for generic dispatch, omni_batch_calculate for chained jobs, omni_describe_solver for schema inspection. Nothing 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.

Deploy Server

Other Tools