Skip to main content
Glama

Sinking Fund Deposit

bpj_sinking_fund_deposit
Read-onlyIdempotent

Calculate the annual end-of-year deposit required to reach a target from an existing reserve at a constant rate.

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": {
      "target": "<target>",
      "savings": "<savings>",
      "years": "<years>",
      "nominal": "<nominal>"
    },
    "name": "bpj_sinking_fund_deposit"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearsYes
targetYes
nominalYes
savingsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds the modelling assumptions (end-of-year, constant rate) but says nothing about edge cases such as savings >= target, a zero nominal rate, or whether the rate is annual-effective versus compounded otherwise. Useful but thin beyond 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?

A single front-loaded sentence with no filler; every clause contributes (action, timing convention, inputs-relationship, rate assumption).

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 four-required-parameter calculation tool with no output schema, the description should state the return value (the annual deposit) and at least the degenerate-rate behavior. It conveys the formula's shape adequately but leaves an agent guessing about units and edge cases.

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 0%, so the description must carry parameter meaning; it maps target, existing reserve (savings) and rate (nominal) conceptually and 'annual' implies years. However it does not clarify that 'nominal' is a percentage, nor the compounding frequency, and leaves 'years' entirely to the schema title.

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?

Names a specific verb and resource ('Calculate the annual end-of-year deposit') plus the key modelling assumptions (target, existing reserve, constant rate). An agent can tell this is a sinking-fund payment solver. It stops short of explicitly naming the returned value as a single deposit amount, but the purpose is unambiguous.

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?

There is no explicit when-to-use or when-not-to-use statement, nor any named alternative. The phrase 'annual end-of-year deposit ... at a constant rate' implicitly scopes it to that payment convention and excludes other timing/compounding variants, which is implied guidance only.

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.