Amaltash Investment & Retirement Calculators

List investments and how each can be used

list_assets

Read-onlyIdempotent

Lists the long-run market rates, which can be used for future plans, and common stocks and funds, which can only be used to look at the past. Stock questions work for any US stock or fund we hold history for, past only. Use it to find a valid long-run rate id.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_assets"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A3.9/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. Beyond that, the description discloses genuinely useful domain behavior: rates are usable for forward-looking planning while stocks/funds are restricted to historical analysis, and stock coverage is limited to instruments we hold history for. That constraint changes how an agent would use the results and is not recoverable from annotations.

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 sentences, front-loaded with the two asset categories and their differing usability. Slightly wasteful: the 'past only' restriction is stated twice (sentence 1 and again as 'past only' in sentence 2), which is redundant wording rather than added information.

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 zero-parameter, read-only listing tool with no output schema, the description covers what the two result categories mean and hints that rate entries carry an id. It does not describe what a stock/fund entry contains or how those entries are keyed, which matters because there is no output schema to fall back on.

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?

The tool takes zero parameters, so the schema cannot explain anything the description needs to compensate for; baseline 4 applies. The description adds nothing parameter-related, which is appropriate here.

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?

The description names a specific verb (lists) and two concrete resources: long-run market rates and common stocks/funds, plus how each category may be used. An agent can tell this is a discovery/enumeration tool. It does not explicitly differentiate itself from siblings such as search_stocks, so it stops short of a 5.

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 to find a valid long-run rate id" gives a clear, actionable when-to-use condition (resolving a prerequisite id for other tools). It also implies the stock/fund listing is for past-only lookups. There is no explicit when-not or named alternative, so it is short of a 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 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?