ClearMind Capital

Search ClearMind Capital's published answers

search_answers

Read-onlyIdempotent

Keyword search over ClearMind Capital's published Q&A answers and Clarity Corner articles on retirement, Social Security, taxes (including Ohio and Columbus), investing, estate planning and trusts, 401(k) and workplace retirement plans, cash balance plans, and working with a fee-only advisor. Returns the best matches, each with the published answer text and its source URL, or an empty list with browse links when nothing matches. No auth; general education only, never advice for a specific person. Use for a specific money question. To browse the library by date or topic use list_clarity_corner; for facts and fees about the firm use get_firm_overview.

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": {
      "query": "<query>"
    },
    "name": "search_answers"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Most results to return (1-10, default 5). Weak matches are dropped, so you may get fewer.
`query`	Yes	The question or topic in plain words, e.g. 'Roth conversion before retirement'. Full questions work; no operators or quotes needed.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 10, 2026

addedInput schema / properties / limit / description

Added value: +"Most results to return (1-10, default 5). Weak matches are dropped, so you may get fewer."

changedInput schema / properties / query / description

Previous value: -"The question or topic, in plain words."New value: +"The question or topic in plain words, e.g. 'Roth conversion before retirement'. Full questions work; no operators or quotes needed."

First observedOct 4, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), and the description still adds substantive behavior: no auth required, general-education-only scope with 'never advice for a specific person', and the exact return contract including the empty-result case with browse links. That is context annotations cannot express.

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-loaded with purpose and return behavior, then the caveat, then routing to siblings. The topic enumeration is long but directly serves retrieval, and no sentence is filler.

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, the description takes on the return contract itself: answer text plus source URL, or an empty list with browse links. Combined with the auth and advice-disclaimer statements, an agent has everything needed to call and interpret this tool.

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?

Schema coverage is 100% and the schema already explains both query (plain words, no operators) and limit (1-10, weak matches dropped). The description's 'keyword search' framing reinforces the query semantics and 'Returns the best matches' implies ranked, non-exhaustive results, but adds little beyond the structured fields. Baseline 3 is appropriate.

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 (keyword search) plus resource (ClearMind Capital's published Q&A answers and Clarity Corner articles) and an explicit topical scope covering retirement, taxes, investing, estate planning and more. It also names two siblings and contrasts itself with them, so an agent can distinguish it without opening any schema.

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?

Gives an explicit trigger ('Use for a specific money question') and explicit routing rules for alternatives: list_clarity_corner for browsing by date or topic, get_firm_overview for firm facts and fees. Both when-to-use and when-to-use-something-else are stated.

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?