Skip to main content
Glama

SIP projection

project_sip
Read-onlyIdempotent

Projected value of a monthly SIP (systematic investment plan) in mutual funds, optionally increased every year (step-up). Assumes the investment is made at the start of each month and compounds monthly at the expected return. Returns are not guaranteed.

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": {
      "monthly_investment": "<monthly_investment>",
      "expected_annual_return": "<expected_annual_return>",
      "years": "<years>"
    },
    "name": "project_sip"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearsYesInvestment period in years
monthly_investmentYesMonthly SIP amount in rupees
annual_step_up_percentNoYearly increase in the SIP amount, % (default 0)
expected_annual_returnYesExpected return, % per year

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this as a read-only, idempotent, closed-world calculation, so the safety profile is covered. The description adds genuinely useful model assumptions: investment at the start of each month, monthly compounding at the expected return, and a step-up applied yearly, plus a 'returns are not guaranteed' caveat. It stops short of stating what the numeric result contains (final corpus vs. invested-vs-gain split).

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 short sentences, front-loaded with what the tool computes, then its modeling assumptions, then the disclaimer. Every clause earns its place and nothing is repeated from the title or annotations.

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 low-complexity, four-parameter calculator the description covers purpose and modeling assumptions well, and annotations cover safety. However, with no output schema in place, the description should indicate what the call returns (a single projected value, and whether invested amount or gain is included), which it leaves ambiguous.

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 100% and every parameter carries its own description and bounds, so the schema does the heavy lifting. The description only re-touches the step-up concept ('optionally increased every year'), adding no syntax, default, or unit information beyond the schema. The one nuance it does add is the start-of-month and monthly-compounding convention, which is timing behavior rather than parameter semantics.

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 gives a specific verb-and-resource: it computes the projected value of a monthly SIP in mutual funds, and it clarifies that the scheme is monthly with an optional yearly step-up. That is enough to separate it from a lumpsum projection conceptually, but it never names or contrasts a sibling (e.g. lumpsum_calculator), so the differentiation is inferred rather than stated.

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 only implied by the tool's narrow subject matter: an agent can tell this is for projecting SIP growth, but there is no explicit when-to-use, when-not-to-use, or alternative-tool routing. No prerequisites or input validity guidance (e.g. minimum monthly amount, year bounds) are mentioned.

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.

Resources