Amaltash Investment & Retirement Calculators

Position Size Calculator

position_size

Read-onlyIdempotent

Position size calculator with an interactive chart. Works out the dollar size of one position at a percent cap the person chooses, how many positions of that size fit, and the amount at risk. It does not pick investments or judge whether a size is suitable.

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": {
      "portfolio_value": "<portfolio_value>",
      "max_position_pct": "<max_position_pct>"
    },
    "name": "position_size"
  }
}

Input Schema

Name	Required	Description
`portfolio_value`	Yes	Total portfolio value in US dollars.
`max_position_pct`	Yes	The cap per position or theme, in percent of the portfolio, the person chose.
`stop_distance_pct`	No	Optional stop distance below entry, in percent. Leave null if there is none.

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?

The annotations already establish that this is read-only, idempotent, closed-world, and non-destructive. The description adds meaningful behavioral context by naming the computed outputs and clarifying that the tool does not make investment recommendations. It does not explain how stop_distance_pct affects the risk calculation, but that is a minor gap given the annotation and schema coverage.

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?

The description is short and front-loaded: it identifies the calculator, states the outputs, then states a scope boundary. Each sentence contributes, though 'with an interactive chart' is contextual rather than essential, and the boundary sentence could be slightly more actionable.

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 three-parameter calculator with full schema descriptions and annotations, the definition covers purpose, computed outputs, and a scope boundary. It omits formula details and the exact role of stop_distance_pct, but an agent has enough information to invoke the tool correctly.

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 all three parameters are already documented in the schema. The description reinforces that max_position_pct is the chosen cap and that portfolio value drives dollar size, but it adds little parameter-level meaning beyond the schema, especially for optional stop_distance_pct. Baseline 3 is appropriate.

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?

It states a specific action and resource: it works out the dollar size of one position, the number of positions, and the amount at risk. That is clear enough to distinguish a position-sizing calculator from sibling calculators, but it does not explicitly differentiate itself from named alternatives.

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?

The description implies use when someone has chosen a percent cap and wants position size, and it explicitly excludes investment picking and suitability judgment. However, it does not state when to use a sibling tool or give an explicit 'use this when' condition, so the guidance is only implied.

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?