ClearMind Capital

ClearMind Capital: firm overview

get_firm_overview

Read-onlyIdempotent

Facts about ClearMind Capital LLC, a fee-only fiduciary registered investment adviser in Columbus, Ohio: services, advisers and credentials, fee schedules, custodian, regulatory IDs (CRD), contact details, and links to the Form ADV summary and SEC record. Takes no arguments, needs no auth, and returns the same published snapshot on every call. Use for any question about the firm itself. For money topics (retirement, taxes, investing) use search_answers; to book a call use get_booking_options; for a company's 401(k) use find_401k_plan.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_firm_overview"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 4, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description still adds genuinely new behavioral facts: it takes no arguments, requires no authentication, and returns the same published snapshot on every call — auth requirements are not expressible in the annotations, so this is real added value.

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?

Front-loaded with the identity and contents, then the invocation contract, then routing. The content enumeration is a long list-in-a-sentence but each item maps to a real capability; slightly dense rather than padded.

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?

There is no output schema, but the description enumerates the returned payload (services, advisers/credentials, fees, custodian, CRD, contact, Form ADV/SEC links), so an agent knows what it will get. Combined with the no-auth/no-arg contract and sibling routing, nothing needed to call it correctly is missing.

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?

Zero parameters, so the baseline is 4. The description explicitly notes it 'takes no arguments', which is consistent with the empty schema and closes off any expectation of filtering options.

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?

Names a specific verb+resource (firm overview / facts about the firm) and enumerates exactly what is covered: services, advisers, fee schedules, custodian, CRD IDs, contacts, Form ADV and SEC links. That level of specificity makes it unmistakable against siblings like search_answers or find_401k_plan.

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 'Use for any question about the firm itself' and then routes three adjacent intents to named alternatives with their triggering conditions (money topics -> search_answers, booking -> get_booking_options, 401(k) -> find_401k_plan). Both when-to-use and when-not-to-use are covered.

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?