Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_motorcycle_loan

Calculate motorcycle loan monthly payments, total interest, and total price paid from price, down payment, APR, and term to avoid manual arithmetic errors.

Instructions

Motorcycle Loan & Financing Calculator. Calculate monthly payments and total interest for new or used motorcycle financing. Discipline: FINANCE. Governing mathematical model / formula: M = P · [r(1 + r)ⁿ] / [(1 + r)ⁿ - 1].

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of moto_payment (Monthly Payment), moto_interest (Total Interest), moto_total (Total Price Paid) using moto_price (Motorcycle Price), moto_down (Down Payment), moto_rate (Interest Rate (%) in %), moto_term (Term (Months) in mo). 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 'Motorcycle Loan & Financing 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): "motorcycle-loan"

    • category (string): "finance"

    • name (string): "Motorcycle Loan & Financing Calculator"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.moto_payment (Monthly Payment): Formatted display string (e.g. '$299.18')

      • metrics.moto_interest (Total Interest): Formatted display string (e.g. '$1,860.64')

      • metrics.moto_total (Total Price Paid): Formatted display string (e.g. '$16,360.64')

    • 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_motorcycle_loan"
  }
}

Input Schema

NameRequiredDescriptionDefault
moto_downNoDown Payment. Cash down payment. Default: 2000. Min: 0. Max: 20000.
moto_rateNoInterest Rate (%) (%). Powersports financing APR. Default: 6.99. Min: 3. Max: 24.
moto_termNoTerm (Months) (mo). Standard 36 to 60 month terms. Default: 48. Min: 24. Max: 84.
moto_priceNoMotorcycle Price. Purchase price of bike. Default: 14500. Min: 2000. Max: 60000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so: it declares read-only, idempotent, stateless behavior with zero side effects, and explains that out-of-bounds inputs return a diagnostic error status instead of throwing. That is precisely the mutation/error-handling information an agent needs before calling.

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?

Sectioned headers (usage, disambiguation, behavior, returns) make it easy to scan, and the core purpose plus formula are front-loaded. It is slightly longer than needed, with mild redundancy between 'Discipline: FINANCE', the formula line, and the RETURNS block, but no sentence is truly wasted.

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?

There is no output schema, and the description compensates with a full return contract: status, calculator, category, formula, echoed inputs with applied defaults, the three metrics with sample formatted values, and execution_time_ms. Combined with validation and routing behavior, an agent has everything needed to call and interpret this tool.

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, and max on every parameter, so the baseline is 3. The description restates parameter names and units and lists computed outputs, but adds little beyond the schema; notably it does not clarify whether moto_rate (annual APR) is converted to a periodic rate before entering the formula, which is the one semantic gap that matters.

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?

The description opens with a specific verb+resource ('Motorcycle Loan & Financing Calculator') and states exactly what it computes: monthly payment and total interest for new or used motorcycle financing. It also names the governing amortization formula, making it trivially distinguishable from adjacent siblings like omni_boat_loan 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?

It supplies explicit WHEN TO USE (map moto_price/moto_down/moto_rate/moto_term to moto_payment/moto_interest/moto_total), WHEN NOT TO USE (qualitative reasoning, non-numerical inputs), and routing rules to omni_universal_query, omni_batch_calculate, and omni_describe_solver. 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