Skip to main content
Glama
Sign In

ClearMind Capital

by com.clearmind-capital
OverviewDiscussionsAdmin

How to contact or book a call with ClearMind Capital

get_booking_options
Read-onlyIdempotent

Booking links and contact details so a person can reach ClearMind Capital themselves. Individuals and families (planning, investments, estate plan) book with the Private Wealth team; business owners and HR leads (401(k), cash balance plans) book with the Workplace Retirement team. Returns links, phone, email, and the client login only. This server never books, submits, or stores anyone's information; hand the links to the person. No auth. For fees, services, or adviser credentials use get_firm_overview.

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_booking_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
audienceNoindividual_or_family for personal planning, business_owner for a company retirement plan. Omit when unsure to get both options.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / audience / description
      Previous value: -"Who is asking. Omit to get both options."New value: +"individual_or_family for personal planning, business_owner for a company retirement plan. Omit when unsure to get both options."
  2. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive, and closed-world, so the safety profile is known. The description goes further by disclosing what the tool will NOT do ('never books, submits, or stores anyone's information; hand the links to the person') and that no auth is required, plus the exact return payload despite no output schema.

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?

Three dense sentences: what it returns, who routes where, and what it never does — each earning its place. The payload description and the non-mutation guarantee are front-loaded before the sibling pointer.

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?

Output schema is absent, but the description enumerates the return contents, removes auth ambiguity, states the non-storing guarantee, and routes to the correct sibling. An agent has everything needed to select and call this tool 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% and the enum self-documents, so baseline is 3. The description adds meaning beyond the enum by mapping each audience value to the specific team that handles it (Private Wealth vs. Workplace Retirement), which helps an agent choose correctly.

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 states a specific verb and resource ('Booking links and contact details'), and immediately narrows scope to what is actually returned ('links, phone, email, and the client login only'). It also distinguishes itself from the sibling get_firm_overview by naming that tool for fees/services/credentials.

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?

It gives explicit routing rules by segment: individuals/families go to Private Wealth, business owners and HR leads go to Workplace Retirement. It also states a clear exclusion ('For fees, services, or adviser credentials use get_firm_overview'), leaving nothing to inference.

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

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