Skip to main content
Glama

finance

Read-only

Calculate compound growth, loan payments, NPV, IRR, CAGR, real returns, and doubling time using percentage rates; performs arithmetic only, not advice.

Instructions

Money math, rates in %: compound (contributions, inflation), loan (payment, interest, amortization), npv, irr, cagr, real_rate, doubling. Arithmetic, not advice.

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": {
      "op": "<op>"
    },
    "name": "finance"
  }
}

Input Schema

NameRequiredDescriptionDefault
opYes
rateNo% per year (npv/irr: per period)
yearsNo
monthsNoloan payments
cashflowsNofrom t=0
end_valueNo
inflationNo%
principalNo
compoundingNoper year, default 12
start_valueNo
contributionNoper period
periods_per_yearNoloan, default 12
contribution_at_startNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds genuinely useful behavioral context (pure arithmetic, not financial advice; rates as percentages) but says nothing about what each op returns, defaults applied beyond the schema, or error behavior for missing parameters.

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?

Extremely compact and front-loaded: domain and unit convention first, then the op inventory, then the scope caveat. Every clause carries information, though the telegraphic parenthetical style borders on under-specification rather than tightness.

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

Completeness3/5

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

For a 13-parameter multi-operation facade with no output schema, the definition is only partially sufficient: the agent knows the op names but not which parameters each op requires or what result each returns. The parenthesis hints help but leave real ambiguity for ops like npv, irr, and cagr.

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?

At 54% schema coverage the description does some compensating work: it associates parameters with ops (contributions and inflation with compound; payment, interest, amortization with loan) and restates the percentage convention. However, seven or so parameters (start_value, end_value, contribution_at_start, compounding, periods_per_year) get no clarification of which op consumes them, leaving the mapping incomplete.

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 domain ("money math") and enumerates every supported operation (compound, loan, npv, irr, cagr, real_rate, doubling), so an agent can match a request to an op without opening the schema. It does not differentiate itself from the sibling "calc" tool, which is the only clarity gap.

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?

"Arithmetic, not advice" usefully bounds the scope and rules out advisory use, and "rates in %" sets a convention. There is no explicit guidance on when to prefer this over the sibling "calc" tool, and no statement of which parameter set applies to each op, so usage must be inferred from the op list.

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