ClearMind Capital

ClearMind 401(k) Scorecard preview

get_401k_scorecard_preview

Read-onlyIdempotent

Preview of the ClearMind 401(k) Scorecard for one plan: overall 0-100 score, band (Strength, Monitor, Priority), headline, and a short story of the plan, scored from its latest public Form 5500-SF filing, with the filing date and data source. Not an audit or compliance determination. The full five-area breakdown is on the Scorecard page, not returned here. No auth. Step 2 of 2: get the plan_id from find_401k_plan first; an unknown plan_id returns an error that says so.

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": {
      "plan_id": "<plan_id>"
    },
    "name": "get_401k_scorecard_preview"
  }
}

Input Schema

Name	Required	Description	Default
`plan_id`	Yes	plan_id from find_401k_plan: 9-digit EIN plus 3-digit plan number, e.g. 341401001-001. The dash is optional.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 10, 2026

changedInput schema / properties / plan_id / description

Previous value: -"plan_id from find_401k_plan, e.g. 341401001-001 (EIN + plan number)."New value: +"plan_id from find_401k_plan: 9-digit EIN plus 3-digit plan number, e.g. 341401001-001. The dash is optional."

First observedOct 4, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses the data provenance (latest public Form 5500-SF filing), that no auth is required, that unknown ids error, and a liability caveat ('Not an audit or compliance determination'). These are meaningful behavioral facts not derivable from the annotations.

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?

Front-loads the return contract first, then caveats, then the sequencing instruction. Every sentence earns its place: scope boundary, provenance, disclaimer, and the step dependency are all distinct and actionable with no redundancy.

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?

No output schema exists, so the description carries the return-value burden and does so fully (score, band, headline, story, filing date, source, and what is omitted). Combined with the readOnly annotations and the prerequisite step, an agent has everything needed to invoke 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?

Schema coverage is 100%, so the schema already documents the single plan_id parameter (EIN+plan number format). The description adds marginal value by tying plan_id to its source tool (find_401k_plan) and its error behavior on unknown values, slightly above the baseline-3 that full schema coverage alone would justify.

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?

Specific verb+resource ('Preview of the ClearMind 401(k) Scorecard for one plan') with an explicit enumeration of what is returned (0-100 score, band values, headline, story, filing date, data source). It also scopes what is NOT returned (the five-area breakdown), which sharply separates it from the Scorecard page and sibling tools.

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 states it is 'Step 2 of 2' and that plan_id must come from find_401k_plan first, naming the prerequisite sibling. It also covers the failure case ('an unknown plan_id returns an error that says so'), so the agent knows both the required sequence and expected behavior on bad input.

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

All ClearMind Capital 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?