Inferventis MCP Server

financial_calculator

Performs precise financial calculations across six calculation types entirely locally with no external API dependency. compound_interest computes the final value and total interest earned on a principal over time at a given annual rate. loan_repayment calculates the monthly payment, total repayable amount, and total interest for a mortgage or loan given the principal, annual rate, and term in months. roi returns return on investment as a percentage and absolute profit or loss, with optional annualised ROI when a holding period is provided. present_value discounts a future cash amount back to its current value using a discount rate. future_value projects a present amount forward at a compounding annual rate. break_even finds the unit volume and revenue at which fixed and variable costs are fully covered by sales. Use this tool when an agent needs to perform any structured financial calculation — loan affordability, investment return, discounted cash flow, or cost analysis. Prefer financial_calculator_lite when only the single headline result is needed rather than a full structured breakdown. Do not use this tool to fetch live market prices or exchange rates — use stock_quote for stock prices, crypto_price for cryptocurrency prices, or currency_convert for FX rates.

Input Schema

TableJSON Schema

Name	Required	Description
`rate`	No	Annual interest or discount rate expressed as a percentage. Example: 5 for 5% per year. Used for compound_interest, loan_repayment, present_value, and future_value.
`periods`	No	Number of time periods. For compound_interest and future_value: years. For loan_repayment: months. For roi: years used for annualised ROI.
`principal`	No	Starting amount or loan amount in your chosen currency. Used for compound_interest, loan_repayment, and future_value calculations.
`final_value`	No	Ending value of an investment or asset. Used for roi and present_value calculations.
`fixed_costs`	No	Total fixed costs of the business or project that do not vary with output volume. Used for break_even calculations.
`discount_rate`	No	Annual discount rate as a percentage for present value calculations. Represents the required rate of return or cost of capital.
`future_amount`	No	The target future cash amount to discount back to present value. Used for present_value calculations.
`initial_value`	No	Starting value of an investment or asset. Used for roi calculations.
`price_per_unit`	No	The selling price per unit of product or service. Used for break_even calculations.
`calculator_type`	Yes	The type of financial calculation to perform. Must be one of: compound_interest, loan_repayment, roi, present_value, future_value, break_even.
`variable_cost_per_unit`	No	The variable cost incurred for each unit produced or sold. Used for break_even calculations.

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations, the description carries the full burden. It discloses that calculations run 'entirely locally with no external API dependency' and details what each calculation type returns (e.g., compound_interest computes final value and total interest; loan_repayment calculates monthly payment, total repayable amount, and total interest). It lacks explicit return format or error behavior, but the output descriptions are substantive. Not contradicting any annotations.

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?

The description is comprehensive yet efficiently structured: one overview sentence, six detailed type sentences, and explicit usage guidance. No fluff or redundant statements. The length is justified by the tool's six calculation types. Everything earns its place.

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?

Given the tool's complexity (six calculation types, 11 parameters, no output schema, no annotations), the description is remarkably complete. It explains each type's computation and key outputs, provides usage context, and distinguishes from siblings. The only missing element is an explicit output structure, but the description already tells the agent what to expect for each calculation.

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 each parameter already well-described (units, examples, which calculations use it). The description adds no new parameter-level meaning beyond the schema; it simply recaps the parameter-to-calculation mapping. Baseline 3 is appropriate since the schema does the heavy lifting.

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 clearly states the tool performs precise financial calculations across six defined types, listing each type and its specific outputs. It distinguishes from siblings by naming alternatives like financial_calculator_lite and market-data tools. The verb 'performs' and resource 'financial calculations' are specific and unambiguous.

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 guidance is provided: 'Use this tool when an agent needs to perform any structured financial calculation', with specific examples. It also states when to prefer financial_calculator_lite and explicitly says not to use this tool for live prices, directing to stock_quote, crypto_price, and currency_convert. This fully covers when/when-not and alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Inferventis MCP Server tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation2/5

Multiple tools have overlapping purposes, particularly the five fiat FX tools (currency_convert, currency_convert_lite, currency_convert_open, currency_fx_lite, currency_rates) and the three crypto tools (crypto_fx_rates, crypto_price, crypto_price_lite). Although descriptions attempt to differentiate them by source or detail level, the boundaries are subtle enough that an agent could easily misselect.

Naming Consistency3/5

Tool names use a mix of noun_noun, noun_verb, and adjective_noun patterns. Some include a 'lite' suffix consistently, but others like 'finnhub_stock_quote' and 'stripe_payment_records' have vendor prefixes, while bank tools lack them. Overall, the naming is readable but lacks a single consistent pattern.

Tool Count3/5

At 20 tools, the server covers a broad scope (finance, news, web, timezone) but includes redundancy (e.g., five FX conversion tools, two financial calculators). The count is not excessive for a general utility server, but it feels slightly bloated due to multiple near-identical variants.

Completeness3/5

The tool set covers many common financial and informational needs, but notable gaps exist: no historical stock data, no support for non-Stripe payment processors, and no ability to initiate payments (read-only). The news sources are limited to BBC and Guardian. Some areas are over-covered while others are missing, resulting in moderate completeness.

Resources

Need Help?