Amaltash Investment & Retirement Calculators

T-Bill Ladder Calculator

tbill_ladder

Read-onlyIdempotent

Treasury bill ladder calculator with an interactive timeline chart. Lays out how much goes in each same-term bill, how far apart to buy them, and the first and last dates. Shows simple interest only if a rate is given.

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": {
      "amount": "<amount>",
      "rungs": "<rungs>",
      "term_weeks": "<term_weeks>",
      "start_date": "<start_date>"
    },
    "name": "tbill_ladder"
  }
}

Input Schema

Name	Required	Description
`rungs`	Yes	How many bills to stagger, a whole number no larger than the term in weeks (13 at most for 52-week bills).
`amount`	Yes	Total dollars to split across the bills, from 0 to 1,000,000,000.
`rate_pct`	No	An annual interest rate the person chooses, in percent, from 0 to 25. Leave out to skip interest.
`start_date`	Yes	The first purchase date, as YYYY-MM-DD.
`term_weeks`	Yes	Length of each bill in weeks: 4, 8, 13, 17, 26 or 52.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so safety is covered; the description adds genuine behavior on top by disclosing that output includes an interactive timeline chart and that interest is only applied when rate_pct is supplied. The conditional response behavior and output shape are exactly the kind of context annotations cannot convey.

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?

Three short sentences, front-loaded with the identity of the tool and followed by output details. No filler, though the sentence about the chart could be merged with the output summary to tighten it further.

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

Completeness4/5

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

For a five-parameter read-only calculator with no output schema, the description covers what is computed, the optional rate path, and the returned chart/schedule at a useful level. An agent has enough to call it correctly; only the precise response payload shape is left implicit.

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%, so the baseline is 3; every parameter including ranges and the term enum is already documented in-schema. The description adds modest framing — that amount is split across equal-term bills, that purchase spacing is derived, and that start_date anchors the first purchase — but stops short of explaining how rungs and term_weeks interact to determine spacing.

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+resource ('Treasury bill ladder calculator') and immediately states what it produces: per-bill amounts, spacing between purchases, and the first/last dates. It is clear what the tool computes, but it never distinguishes itself from the many sibling finance calculators (e.g. compound_interest, plan_recurring_investment), so an agent must infer the boundary.

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?

Usage is implied rather than stated: an agent can infer this is the tool for staggering same-term T-bills, and the conditional 'only if a rate is given' hints at an optional interest mode. There is no explicit when-to-use, when-not-to-use, or named alternative among the sibling calculators.

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

All Amaltash Investment & Retirement Calculators tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?