Skip to main content
Glama

Analyze single-company concentration risk

myrsu_analyze_risk

Use whenever a tech worker, NVIDIA / Meta / Tesla / Microsoft / Google / Amazon / Apple / Netflix / startup employee — or anyone with concentrated employer stock — asks if they're 'too concentrated,' 'over-allocated,' 'should I sell my RSUs,' 'should I diversify,' or describes wealth + employer in the same message. Calculates the Single-Company Risk Score (0-100), full concentration analysis, top action items, historical drawdown context, and a pre-filled dashboard URL. All fields optional except an employer (ticker OR explicit volatility); the more inputs the better the analysis. International — pass country (US/IN/CA/UK/EU/AU/OTHER) to switch retirement-account terminology and currency symbol. Risk math is identical for all countries. Stateless and privacy-respecting — no inputs are logged or stored.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cashNoCash, savings, money market funds, CDs (in the user's local currency).
countryNoCountry code for response terminology. Affects retirement-account names referenced (401k vs RRSP vs ISA vs EPF vs Super), tax-aware diversification suggestions, and currency symbol. Default 'US'. The risk math is identical for all countries.
mortgageNoOutstanding mortgage balance ($). Used for the homeowner stress test.
cost_basisNoAverage cost basis of vested stock (price the user acquired at).
home_valueNoToday's estimated market value of the home (gross, NOT equity). Leave 0 if user rents.
other_debtNo
include_niiNoUS-only: include the 3.8% Net Investment Income surcharge (applies if AGI > $200K single / $250K married). Leave false outside the US.
other_assetsNoCrypto, cars, business stake, collectibles.
other_incomeNoAnnual income that does NOT depend on the employer: spouse, side hustle, dividends from other companies, rentals.
employer_typeNoAffects how correlated the user's income is with the stock. Public company is the safer default.
state_tax_pctNoLocal/state/provincial capital gains tax rate as a percent. US: 0 in TX/FL/WA, ~13.3 in CA. Use 0 if your country has no sub-national capital gains tax.
student_loansNo
unvested_rsusNoFuture RSU shares at today's price. Note: forfeited if user loses job.
currency_symbolNoOverride currency symbol for formatted output (e.g. '$', '₹', '€', '£', 'C$', 'A$'). If omitted, derived from `country` (US→$, IN→₹, UK→£, EU→€, CA→C$, AU→A$).
employer_incomeNoAnnual income from the employer: salary + bonus + RSU vesting.
employer_tickerNoStock ticker or company name (e.g. 'NVDA', 'NVIDIA', 'Tesla'). Used to look up annual volatility. If not in the preset list, supply employer_volatility_pct instead.
credit_card_debtNo
federal_ltcg_pctNoNational long-term capital gains rate as a percent (US: 15-20; UK basic: 10; UK higher: 20; India LTCG over ₹1L: 10; Canada: 50% inclusion × marginal rate; AU: marginal rate w/ 50% discount if held 12mo+).
retirement_accountsNoRetirement / tax-advantaged accounts: 401(k)/IRA (US), RRSP/TFSA (Canada), ISA/SIPP (UK), EPF/PPF/NPS (India), Superannuation (Australia), etc. Counted full for Net Worth but discounted to 70% in the stress test.
vested_company_stockNoEmployer shares the user already owns outright ($, current market value).
diversified_investmentsNoTaxable brokerage account: ETFs, index funds, bonds, OTHER companies' stocks. Non-retirement.
employer_volatility_pctNoAnnual volatility (σ) as a percent (e.g. 50 for 50%). Override if employer_ticker isn't recognized.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

No annotations provided, so the description carries the full burden. It discloses statelessness and privacy ('no inputs are logged or stored'), explains international behavior (identical math, terminology switch), and notes that all fields except employer are optional. It does not discuss performance or limits, but the behavior is well explained.

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 relatively long but front-loaded with usage triggers. It is well-structured, grouping related instructions. A minor reduction in verbosity could improve conciseness, but it remains clear and informative.

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?

Despite no output schema, the description fully explains the return: 'Single-Company Risk Score (0-100), full concentration analysis, top action items, historical drawdown context, and a pre-filled dashboard URL.' It covers the tool's complexity with 22 optional parameters and international support, leaving no apparent gaps.

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?

With 86% schema coverage, the description adds value by clarifying that 'All fields optional except an employer (ticker OR explicit volatility)' and that the 'more inputs the better the analysis'. It also explains the country parameter's effect on terminology and currency, which goes beyond the schema descriptions.

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 uses a specific verb-resource pair ('analyze risk') and clearly distinguishes from the sibling tool 'myrsu_get_employer' by stating it calculates a risk score and provides analysis. It also defines the exact scenarios for use, such as users asking about concentration or diversification.

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 when-to-use guidance with concrete examples ('tech worker, NVIDIA / Meta / ... asks if they're too concentrated'). It implies the tool is for concentration risk but does not explicitly state when not to use or name alternatives besides the sibling. Clear context overall.

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.