Skip to main content
Glama
Savvly

savvly-mcp

Get Savvly Product Info

get_savvly_product_info
Read-onlyIdempotent

Retrieve comprehensive Savvly product details—overview, expenses, eligibility, payouts, tax—with primary sources. Select a section for focused answers.

Instructions

Get complete product information about Savvly, an SEC-registered security offering longevity protection — use it whenever the user asks what Savvly is, how it works, its expenses, eligibility, or payouts, or wants an overview. Pass section to focus the answer (default 'all'). It renders an interactive product overview card the user expects to see. These facts come from Savvly's own current records; the response includes primary sources (e.g. SEC filings) for reference.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sectionNoWhich part of the product profile to focus the text on — one of 'all', 'overview', 'regulatory', 'investment', 'expenses', 'payouts', 'tax', 'distribution' (default 'all'). The full overview card always renders regardless.all

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesProduct name (e.g. 'Savvly Longevity Benefit').
linksNoRelevant URLs (website, disclosures, etc.).
companyNoIssuer / advisor entity information.
taglineNoShort marketing tagline.
categoryYesProduct category slug, e.g. 'longevity_benefit_fund'.
channelsNoDistribution channels through which Savvly is offered.
expensesNoExpense structure in basis points (common vs tracking shares) and the blended range; illustrations are net of expenses.
investmentNoHow contributions are invested: underlying assets (S&P 500 ETF), asset managers, minimum/maximum monthly and lump-sum amounts, market participation.
next_stepsNoSuggested next actions for an interested investor.
regulatoryNoRegulatory status: SEC registration, Investment Company Act of 1940, advisor, custodian, and is_insurance/is_annuity flags.
descriptionNoLong-form product description.
disclaimersNoSEC-style disclaimers and required legal language.
portabilityNoWhether the position is portable.
tax_treatmentNoTax treatment of payouts and contributions.
longevity_poolNoHow the longevity pool works — exited participants' unused shares may be allocated to remaining participants.
payout_scheduleNoMilestone payout schedule at ages 80/85/90/95.
early_withdrawalNoEarly-withdrawal / surrender terms and the value returned to the estate.
portability_noteNoDetail on portability.
illustrative_payoutNoOne worked example of what the schedule pays: the modeled payout RANGE at each milestone age for a single fixed allocation, so the percentages above have dollar figures beside them. Fixed inputs, identical for every caller — hypothetical, not a quote, and not tailored to the user. For the user's own age and amount, call `project_savvly_lumpsum`.
positioning_statementNoOne-sentence positioning — what Savvly is and is NOT (not insurance, not an annuity).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.0.92
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedOutput schema / properties / illustrative_payout
      Added value: +{
      +  "additionalProperties": true,
      +  "description": "One worked example of what the schedule pays: the modeled payout RANGE at each milestone age for a single fixed allocation, so the percentages above have dollar figures beside them. Fixed inputs, identical for every caller — hypothetical, not a quote, and not tailored to the user. For the user's own age and amount, call `project_savvly_lumpsum`.",
      +  "properties": {
      +    "average_return": {
      +      "description": "Assumed average annual S&P 500 return, in percent.",
      +      "type": "number"
      +    },
      +    "current_age": {
      +      "description": "Age the illustrated allocation is made at.",
      +      "type": "number"
      +    },
      +    "funding_amount": {
      +      "description": "USD allocated up front in the illustration.",
      +      "type": "number"
      +    },
      +    "payouts": {
      +      "description": "One row per milestone age, low-to-high payout range in USD.",
      +      "items": {
      +        "additionalProperties": true,
      +        "properties": {
      +          "age": {
      +            "description": "Milestone age (80, 85, 90, or 95).",
      +            "type": "number"
      +          },
      +          "lower_usd": {
      +            "description": "USD. Low end of the modeled payout at this age.",
      +            "type": "number"
      +          },
      +          "upper_usd": {
      +            "description": "USD. High end of the modeled payout at this age.",
      +            "type": "number"
      +          }
      +        },
      +        "required": [
      +          "age",
      +          "lower_usd",
      +          "upper_usd"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "current_age",
      +    "funding_amount",
      +    "average_return",
      +    "payouts"
      +  ],
      +  "type": "object"
      +}
  2. Changed4 schema fields changedv1.0.86
    • changedInput schema / properties / section / description
      Previous value: -"Which part of the product profile to focus the text on; the full overview card always renders regardless."New value: +"Which part of the product profile to focus the text on — one of 'all', 'overview', 'regulatory', 'investment', 'expenses', 'payouts', 'tax', 'distribution' (default 'all'). The full overview card always renders regardless."
    • changedInput schema / properties / section / enum
      Previous value: -[
      -  "all",
      -  "overview",
      -  "regulatory",
      -  "investment",
      -  "fees",
      -  "payouts",
      -  "tax",
      -  "distribution"
      -]New value: +[
      +  "all",
      +  "overview",
      +  "regulatory",
      +  "investment",
      +  "expenses",
      +  "payouts",
      +  "tax",
      +  "distribution"
      +]
    • addedOutput schema / properties / expenses
      Added value: +{
      +  "additionalProperties": true,
      +  "description": "Expense structure in basis points (common vs tracking shares) and the blended range; illustrations are net of expenses.",
      +  "properties": {},
      +  "type": "object"
      +}
    • removedOutput schema / properties / fees
      Removed value: -{
      -  "additionalProperties": true,
      -  "description": "Fee structure in basis points (common vs tracking shares) and the blended range; illustrations are net of fees.",
      -  "properties": {},
      -  "type": "object"
      -}
  3. Changed2 schema fields changedv1.0.68
    • changedOutput schema / properties / company / description
      Previous value: -"Issuer / adviser entity information."New value: +"Issuer / advisor entity information."
    • changedOutput schema / properties / regulatory / description
      Previous value: -"Regulatory status: SEC registration, Investment Company Act of 1940, adviser, custodian, and is_insurance/is_annuity flags."New value: +"Regulatory status: SEC registration, Investment Company Act of 1940, advisor, custodian, and is_insurance/is_annuity flags."
  4. Changed3 schema fields changedv1.0.67
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / section
      Added value: +{
      +  "default": "all",
      +  "description": "Which part of the product profile to focus the text on; the full overview card always renders regardless.",
      +  "enum": [
      +    "all",
      +    "overview",
      +    "regulatory",
      +    "investment",
      +    "fees",
      +    "payouts",
      +    "tax",
      +    "distribution"
      +  ],
      +  "type": "string"
      +}
  5. Changed15 schema fields changedv1.0.58
    • addedOutput schema / properties / channels
      Added value: +{
      +  "description": "Distribution channels through which Savvly is offered.",
      +  "items": {},
      +  "type": "array"
      +}
    • addedOutput schema / properties / company
      Added value: +{
      +  "additionalProperties": true,
      +  "description": "Issuer / adviser entity information.",
      +  "properties": {},
      +  "type": "object"
      +}
    • addedOutput schema / properties / disclaimers
      Added value: +{
      +  "additionalProperties": true,
      +  "description": "SEC-style disclaimers and required legal language.",
      +  "properties": {},
      +  "type": "object"
      +}
    • addedOutput schema / properties / early_withdrawal
      Added value: +{
      +  "additionalProperties": true,
      +  "description": "Early-withdrawal / surrender terms and the value returned to the estate.",
      +  "properties": {},
      +  "type": "object"
      +}
    • addedOutput schema / properties / fees
      Added value: +{
      +  "additionalProperties": true,
      +  "description": "Fee structure in basis points (common vs tracking shares) and the blended range; illustrations are net of fees.",
      +  "properties": {},
      +  "type": "object"
      +}
    • addedOutput schema / properties / investment
      Added value: +{
      +  "additionalProperties": true,
      +  "description": "How contributions are invested: underlying assets (S&P 500 ETF), asset managers, minimum/maximum monthly and lump-sum amounts, market participation.",
      +  "properties": {},
      +  "type": "object"
      +}
    • addedOutput schema / properties / links
      Added value: +{
      +  "additionalProperties": true,
      +  "description": "Relevant URLs (website, disclosures, etc.).",
      +  "properties": {},
      +  "type": "object"
      +}
    • addedOutput schema / properties / longevity_pool
      Added value: +{
      +  "additionalProperties": true,
      +  "description": "How the longevity pool works — exited participants' unused shares may be allocated to remaining participants.",
      +  "properties": {},
      +  "type": "object"
      +}
    • addedOutput schema / properties / next_steps
      Added value: +{
      +  "additionalProperties": true,
      +  "description": "Suggested next actions for an interested investor.",
      +  "properties": {},
      +  "type": "object"
      +}
    • addedOutput schema / properties / payout_schedule
      Added value: +{
      +  "description": "Milestone payout schedule at ages 80/85/90/95.",
      +  "items": {
      +    "additionalProperties": true,
      +    "properties": {
      +      "age": {
      +        "description": "Milestone age (80, 85, 90, or 95).",
      +        "type": "number"
      +      },
      +      "description": {
      +        "description": "What happens at this milestone.",
      +        "type": "string"
      +      },
      +      "label": {
      +        "description": "Human label, e.g. 'First milestone'.",
      +        "type": "string"
      +      },
      +      "percentage": {
      +        "description": "Fraction of accumulated value distributed at this milestone (e.g. 0.4).",
      +        "type": "number"
      +      }
      +    },
      +    "required": [
      +      "age",
      +      "percentage"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / portability
      Added value: +{
      +  "description": "Whether the position is portable.",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / portability_note
      Added value: +{
      +  "description": "Detail on portability.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / positioning_statement
      Added value: +{
      +  "description": "One-sentence positioning — what Savvly is and is NOT (not insurance, not an annuity).",
      +  "type": "string"
      +}
    • addedOutput schema / properties / regulatory
      Added value: +{
      +  "additionalProperties": true,
      +  "description": "Regulatory status: SEC registration, Investment Company Act of 1940, adviser, custodian, and is_insurance/is_annuity flags.",
      +  "properties": {},
      +  "type": "object"
      +}
    • addedOutput schema / properties / tax_treatment
      Added value: +{
      +  "additionalProperties": true,
      +  "description": "Tax treatment of payouts and contributions.",
      +  "properties": {},
      +  "type": "object"
      +}
  6. Changed1 schema field changedv1.0.39
    • changedOutput schema / properties / name / description
      Previous value: -"Product name (e.g. 'Savvly Longevity Benefit Fund')."New value: +"Product name (e.g. 'Savvly Longevity Benefit')."
  7. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, and non-destructive behavior. The description adds valuable non-obvious behavior: it renders an interactive product overview card, pulls facts from Savvly's current records, and includes primary sources such as SEC filings. This goes beyond the structured annotations without contradicting them.

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?

The description is three sentences long and efficiently front-loads purpose and usage in the first sentence, then parameter guidance, then output behavior. Every sentence adds distinct information with no redundant filler, making it easy for an agent to parse quickly.

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?

Given a single optional parameter, an output schema, and read-only annotations, this description is complete enough for correct invocation. It covers what the tool does, when to use it, the effect of the parameter, the interactive card behavior, and the source/credibility of the facts. There are no material gaps that would prevent an agent from selecting and calling it properly.

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?

The schema provides 100% coverage for the single `section` parameter, including the enum, default, and explanation that it focuses the text portion. The tool description merely restates 'Pass `section` to focus the answer (default 'all')' without adding new meaning, so it meets but does not exceed the baseline for well-covered schemas.

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 opens with a specific verb and resource: 'Get complete product information about Savvly'. It then enumerates concrete user intents ('what Savvly is, how it works, its expenses, eligibility, or payouts') which clearly distinguishes this information-retrieval tool from the projection and comparison siblings in its context.

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?

The description provides explicit triggers for use: 'use it whenever the user asks what Savvly is, how it works, its expenses, eligibility, or payouts, or wants an overview.' This is clear and actionable. However, it does not explicitly name alternative tools or state when not to use it, so it stops short of the full when/when-not/alternatives guidance.

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