Skip to main content
Glama

Inferventis — Financial Data, News & Web MCP

by io.github.jonathanpchapman

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
NameRequiredDescriptionDefault
rateNoAnnual 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.
periodsNoNumber of time periods. For compound_interest and future_value: years. For loan_repayment: months. For roi: years used for annualised ROI.
principalNoStarting amount or loan amount in your chosen currency. Used for compound_interest, loan_repayment, and future_value calculations.
final_valueNoEnding value of an investment or asset. Used for roi and present_value calculations.
fixed_costsNoTotal fixed costs of the business or project that do not vary with output volume. Used for break_even calculations.
discount_rateNoAnnual discount rate as a percentage for present value calculations. Represents the required rate of return or cost of capital.
future_amountNoThe target future cash amount to discount back to present value. Used for present_value calculations.
initial_valueNoStarting value of an investment or asset. Used for roi calculations.
price_per_unitNoThe selling price per unit of product or service. Used for break_even calculations.
calculator_typeYesThe type of financial calculation to perform. Must be one of: compound_interest, loan_repayment, roi, present_value, future_value, break_even.
variable_cost_per_unitNoThe variable cost incurred for each unit produced or sold. Used for break_even calculations.

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries the full transparency burden. It discloses that calculations run 'entirely locally with no external API dependency' and specifies what each calculation returns (e.g., 'returns return on investment as a percentage and absolute profit or loss'). This gives the agent a clear behavioral contract without relying on structured 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?

While the description is long (~200 words), every sentence earns its place: it front-loads the core purpose, then systematically details each calculation type, followed by usage guidance and exclusions. The structure is logical and not redundant, making the length justifiable for a multi-purpose tool.

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 (11 parameters, no output schema, no annotations), this description is exceptionally complete. It covers all six calculation types with their inputs and outputs, explains when to use this tool vs alternatives, and explicitly warns against misuse for market data. No significant gaps remain.

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 each parameter already has a detailed description including units and applicable calculation types. The tool description echoes these details (e.g., periods: years vs months) but adds no new parameter-level information beyond what the schema already provides. Baseline 3 is appropriate because 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 starts with a specific verb ('Performs precise financial calculations') and enumerates all six calculation types with their exact outputs. It clearly distinguishes this tool from siblings by naming financial_calculator_lite and market data tools, making the purpose unmistakable.

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 guidance is provided ('Use this tool when an agent needs to perform any structured financial calculation'). When-not-to-use is also clear: 'Do not use this tool to fetch live market prices or exchange rates,' with named alternatives (stock_quote, crypto_price, currency_convert). Additionally, it tells when to prefer financial_calculator_lite over this tool.

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

All Inferventis — Financial Data, News & Web MCP toolsInspect
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
Disambiguation3/5

Many tools have overlapping purposes, especially in currency conversion (5 tools) and financial calculations (2 tools). While descriptions are detailed and try to differentiate, the sheer number of similar tools could confuse an agent. The platform_tool_finder tool helps but doesn't fully resolve ambiguity.

Naming Consistency3/5

Naming follows snake_case but is inconsistent: some tools use noun_verb (e.g., currency_convert), others noun_noun (e.g., bank_accounts). There are also variants with suffixes like '_lite' and '_open' which help, but the pattern varies across the set.

Tool Count4/5

20 tools is reasonable for a financial data and news server, covering stocks, crypto, fiat, banking, payments, calculations, and web content. However, there is redundancy (5 fiat converters) that could be streamlined, making the count slightly higher than ideal.

Completeness4/5

The tool set covers a broad range of financial tasks: real-time stocks, crypto, fiat conversion, bank transactions, payments, financial calculations, news, and web reading. Minor gaps exist, such as lack of historical stock data or portfolio tracking, but most common queries can be handled.

Resources