MySSAgent Social Security Claiming Estimator

Start a new client's claiming analysis

start_client_analysis

For financial advisors (sign in with your myssagent.com account when prompted; an advisor account is not needed yet). Use it when the advisor wants to add a new client or run MySSAgent's analysis for a client who is not on their roster yet. Takes only the client's name, marital status and, for a married client, the spouse's name, and returns one myssagent.com link where the advisor finishes: opening an advisor account if they have none, uploading the client's SSA statement (the birth dates and earnings record come from it), and running the analysis; a pay-per-client account pays for the household there, from its wallet. Nothing runs and nothing is charged in this conversation. Never pass a Social Security number, a birth date or an account number. After the advisor finishes on the page, list_clients and get_client_report return the new client here.

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": {
      "client_name": "<client_name>",
      "marital_status": "<marital_status>"
    },
    "name": "start_client_analysis"
  }
}

Input Schema

Name	Required	Description
`client_name`	Yes	The client's name as the advisor gave it.
`spouse_name`	No	Married clients only, optional: the spouse's name.
`marital_status`	Yes	The client's marital status.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 30, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations, it discloses the sign-in prompt, that an advisor account is not needed yet, that the tool returns a link for SSA upload and analysis, and that nothing runs or is charged in this conversation. It also explains the pay-per-client wallet behavior and forbids passing SSNs, birth dates, or account numbers.

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 dense and front-loads the audience and usage before the workflow and safety constraints. It is somewhat long and packs the link workflow into a complex sentence, but nearly every clause carries useful calling information.

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?

With no output schema, it still explains the returned link, where the advisor finishes, the lack of charge or execution in this conversation, and how completion surfaces via list_clients and get_client_report. That covers the operational context an agent needs to call it correctly.

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?

The schema already documents all three parameters at 100% coverage, but the description reinforces that only name, marital status, and, for married clients, spouse name are needed. It also adds a valuable negative constraint against passing sensitive identifiers such as SSN, birth date, or account number.

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 and resource, starting a new client's claiming analysis, and clearly scopes it to advisors adding a client who is not yet on their roster. It also distinguishes the tool from follow-up siblings by explaining that after completion list_clients and get_client_report return the new client.

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?

It gives a clear use case: the advisor wants to add a new client or run analysis for a client not on their roster yet, and it notes the myssagent.com sign-in prompt. However, it does not explicitly route existing-roster clients to run_client_analysis or state exclusions beyond the roster condition.

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

All MySSAgent Social Security Claiming Estimator 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?