Skip to main content
Glama
Savvly

savvly-mcp

Project Retirement Trajectory With Savvly

project_retirement_with_savvly
Read-onlyIdempotent

Simulates retirement savings trajectory with and without a Savvly allocation, providing gap score and possible higher monthly paycheck.

Instructions

Full retirement simulation showing the projected savings trajectory WITH and WITHOUT a Savvly allocation across the planning horizon (current_age → life_expectancy). Returns gap_score, possible_higher_monthly_paycheck, a server-provided headline message, and a per-year age_dependent_values[] timeline. Disclaimers + per-field hints under metadata. DISCLOSURE REQUIRED: display disclosure.text verbatim and link disclosure.url to the user alongside any figures from this response. Required by SEC Marketing Rule and FINRA Rule 2210 — do not paraphrase or omit. VISUALIZATION: this tool emits an interactive chart widget (MCP Apps — see _meta.ui). MCP-Apps-capable hosts render it inline and editable; other clients render only your text and show no chart. Do NOT draw, generate, or render your own chart, graph, or table of these numbers — there is no fallback chart for you to build, so never produce a duplicate. Do NOT claim or imply a chart is visible (avoid 'the chart above shows…'); you cannot tell whether the host rendered the widget. Summarize the key figures in prose and show the disclosure text and link, and reference the chart only conditionally (e.g. 'if your client shows the interactive chart, its fields are editable to re-run the projection'). INPUTS: every parameter is OPTIONAL and defaults to a sensible value. Call this tool IMMEDIATELY — pass only the values the user explicitly stated and omit the rest. Do NOT ask the user for starting values, assumptions, or missing parameters before calling; the rendered widget has editable fields so they adjust age, amounts, and other assumptions inline after it appears.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
current_ageNoCurrent age (default 40)
retirement_ageNoPlanned retirement age (default 68)
life_expectancyNoPlanning horizon (default 100)
monthly_contributionNoMonthly retirement contribution in USD (default 1000)
current_retirement_savingsNoCurrent total retirement savings in USD (default 60000)
monthly_paycheckNoDesired monthly retirement paycheck in USD (default 4500)
other_retirement_incomeNoOther monthly retirement income in USD (default 1600)
annual_income_increaseNoAnnual contribution % increase (default 2)
percentage_in_savvlyNoPercentage of the retirement portfolio allocated to Savvly (default 5)
pre_retirement_returnNoExpected pre-retirement annual return % (default 6)
post_retirement_returnNoExpected post-retirement annual return % (default 5)
inflation_rateNoExpected annual inflation rate % (default 3)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputsYes
resultYes
summaryYesConvenience summary. The narrative carries the canonical full-disclosures URL inline; display it verbatim alongside any figures from this response.
visualizationNoRecommended chart for this projection — a year-by-year area chart of `result.age_dependent_values` (savings with vs. without Savvly). Render it when the surface can display a graph. The richer `metadata.display_hints` block carries the same chart plus layout/tooltip detail.
disclosureYesDISCLOSURE REQUIRED: display `disclosure.text` and link `disclosure.url` to the user whenever you present any number from this response. Required by SEC Marketing Rule and FINRA Rule 2210.
metadataYes
Behavior5/5

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

Discloses detailed output handling: mandatory display of disclosure text/link for SEC/FINRA compliance, and precise instructions about the interactive chart widget (no fallback, no duplicate, conditional reference). Adds significant behavioral context beyond the safe read-only 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?

The description is lengthy but well-structured into paragraphs: purpose, output, disclosure, visualization, usage, and optionality. Every sentence serves a purpose, and key information is front-loaded. Minor verbosity is justified by the tool's complexity.

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

Completeness5/5

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

Covers all aspects: purpose, output fields, mandatory disclosure, visualization behavior, parameter optionality, and call urgency. Given the rich annotations and output schema, nothing essential is missing.

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?

All 12 parameters have descriptions in the schema (100% coverage), so the description adds little per-parameter meaning. However, it highlights that all parameters are optional with sensible defaults, which is useful but not schema-surpassing.

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 clearly states it's a 'full retirement simulation' comparing with and without Savvly, differentiating it from sibling tools like project_savvly_lumpsum or project_savvly_monthly which are simpler projections. The verb 'simulate' and resource 'retirement trajectory with Savvly' are specific and unambiguous.

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

Usage Guidelines5/5

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

Explicitly instructs to call the tool 'IMMEDIATELY' without asking user for missing parameters, emphasizing that all parameters are optional with defaults. This provides clear guidance on when to use the tool and how to handle input, avoiding unnecessary back-and-forth.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Savvly/savvly-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server