Skip to main content
Glama

Valor del dinero en el tiempo

fin-tvm
Read-onlyIdempotent

Resuelve la variable faltante del valor del dinero en el tiempo (pv, fv, pmt, nper o tasa). Cuándo: un cálculo de dinero, impuestos o matemática financiera tiene que ser exacto y reproducible (redondeo, centavos, tasas). No para: calcular la cuota fija de un préstamo amortizable (fin-loan-payment). Efectos secundarios: ninguno (solo lectura, sin red, sin estado guardado). Determinista: la misma entrada da la misma salida. Límites: entrada JSON de hasta 64 KB, 1 s por llamada, resultado de hasta 1 MB.

EN: Solves for the one missing TVM variable (pv, fv, pmt, nper or rate per period) given the others, with Excel sign convention (cash out negative) and payments at end or beginning. When: a money, tax or financial-math result has to be exact and reproducible (rounding, cents, rates). Not for: computing the fixed periodic payment for an amortizing loan: PMT = P·r / (fin-loan-payment). Side effects: none (read-only, no network access, no stored state). [EN completo / full EN: inputSchema.description]

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pv": 200000,
      "nper": 360,
      "rate": 0.005,
      "solve_for": "pmt"
    },
    "name": "fin-tvm"
  }
}

Input Schema

NameRequiredDescriptionDefault
fvNoFuture value (number; optional).
pvNoPresent value (number; optional).
pmtNoPayment per period (number; optional).
nperNoNumber of periods (number; optional; min 0; max 10000).
rateNoInterest rate per period as a decimal (0.05 = 5%) (number; optional; min -0.99; max 10).
whenNoPayment timing (optional; one of: end, begin; default "end").end
solve_forYesUnknown (required; one of: pv, fv, pmt, nper, rate).

Output Schema

NameRequiredDescriptionDefault
fvNo
pmtNo
nperNo
rateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "nper": 360,
      +    "pv": 200000,
      +    "rate": 0.005,
      +    "solve_for": "pmt"
      +  }
      +]
  2. Changed1 schema field changed
    • addedInput schema / properties / solve_for / examples
      Added value: +[
      +  "pmt"
      +]
  3. Changed1 schema field changed
    • addedInput schema / description
      Added value: +"EN: Solves for the one missing TVM variable (pv, fv, pmt, nper or rate per period) given the others, with Excel sign convention (cash out negative) and payments at end or beginning. When: a money, tax or financial-math result has to be exact and reproducible (rounding, cents, rates). Not for: computing the fixed periodic payment for an amortizing loan: PMT = P·r / (fin-loan-payment). Side effects: none (read-only, no network access, no stored state). Deterministic: the same input gives the same output. Limits: JSON input up to 64 KB, 1 s per call, result up to 1 MB."
  4. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so 'no side effects / read-only / no network' restates them. What the description adds beyond annotations is real: determinism, sign convention, payment timing, and concrete limits (64 KB input, 1 s per call, 1 MB result). Return values are not described, but an output schema exists to cover that.

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?

Front-loaded with the core operation and organized under clear labels (When / Not for / Side effects / Deterministic / Limits). The main cost is that the whole block is presented twice, in Spanish and English, with the English version truncated into a pointer to inputSchema.description — redundancy that dilutes conciseness without adding information.

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?

Everything an agent needs to call this correctly is present: required parameter (solve_for), the five solvable variables, sign convention, timing option, determinism, size/time limits, and sibling routing. An output schema exists, so omitting return-value detail is appropriate rather than a gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3, but the description adds genuine interpretation guidance beyond the schema: the Excel cash-out-negative sign convention and the end-vs-begin payment timing, both of which determine how pv/fv/pmt must be signed and are absent from the field descriptions. It does not restate rate-as-decimal or the nper bounds, which is fine since the schema already does.

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 operation on a specific resource: solves for the single missing TVM variable (pv, fv, pmt, nper or rate) given the others. It also pins down semantics (Excel sign convention, payments at end or beginning) and explicitly distinguishes itself from the nearest sibling, fin-loan-payment.

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?

Has an explicit 'Cuándo' section (money/tax/financial-math results that must be exact and reproducible) and an explicit 'No para' section routing the amortizing-loan-payment case to fin-loan-payment. Both the inclusion and exclusion conditions are stated, not left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources