Skip to main content
Glama
Sign In

Amaltash Investment & Retirement Calculators

by com.amaltash
OverviewDiscussionsAdmin

Net Worth Calculator

net_worth_check
Read-onlyIdempotent

Net worth calculator with an interactive chart. Subtracts debts from assets and, when an age is given, shows the median net worth for that age group from a US government survey. Use it for a net worth total or a net worth by age comparison.

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": {
      "assets": "<assets>",
      "debts": "<debts>"
    },
    "name": "net_worth_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
ageNoAge in whole years, from 18 to 110, to compare with others that age.
debtsYesTotal of everything owed, as a positive number of US dollars.
assetsYesTotal value of everything owned, in US dollars.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world behavior, so the description's job is to add more — and it does: the age-triggered comparison branch, the external data source (US government survey), and the presence of an interactive chart. It does not describe the response shape or numeric formatting, leaving a small gap.

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?

Three tight sentences with the core operation front-loaded, followed by the conditional behavior and then usage framing. No filler or restatement of the title.

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?

With no output schema, the description does explain what comes back (a net worth total and, with age, a median comparison), which is the key omission risk for this tool. It could still say more about the returned figure's currency/formatting and how the chart appears, so it is not fully complete.

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 schema already documents units, ranges, and the positive-value convention for debts. The description reinforces the assets-minus-debts relationship and the optional age path, but adds little syntax or meaning the schema does not already carry; baseline 3 applies.

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 names the specific operation (subtract debts from assets) and the conditional extension (median net worth for an age group from a US government survey). An agent can tell this apart from siblings like compound_interest or retirement_plan without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use it for a net worth total or a net worth by age comparison' gives clear positive usage context for both modes. It stops short of naming alternatives or stating when not to use it, so it lands at 4 rather than 5.

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 toolsInspect
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