Skip to main content
Glama
Sign In

ClearMind Capital

by com.clearmind-capital
OverviewDiscussionsAdmin

List Clarity Corner articles and videos

list_clarity_corner
Read-onlyIdempotent

List ClearMind Capital's Clarity Corner education library, newest first, with titles, summaries, dates, and URLs. Every result also includes the full list of topic names, so call it with no arguments first to see which topics exist. No auth. Use to browse or find recent content. To answer a specific question use search_answers, which ranks by relevance instead of date.

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": "list_clarity_corner"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoArticle, Video, Short, or Podcast. Case-insensitive; plurals work.
limitNoMost items to return (1-25, default 10).
topicNoTopic name or part of one, case-insensitive, e.g. 'Retirement' or 'tax'. Combines with kind (both must match).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / kind / description
      Previous value: -"Article, Video, Short, or Podcast."New value: +"Article, Video, Short, or Podcast. Case-insensitive; plurals work."
    • addedInput schema / properties / limit / description
      Added value: +"Most items to return (1-25, default 10)."
    • changedInput schema / properties / topic / description
      Previous value: -"Topic name or part of one, e.g. 'Retirement' or 'Taxes'."New value: +"Topic name or part of one, case-insensitive, e.g. 'Retirement' or 'tax'. Combines with kind (both must match)."
  2. First observed

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 useful behavior beyond that: no authentication required, newest-first ordering, and the fact that every result embeds the full topic list for discovery. It does not mention pagination beyond the limit param, which keeps it from a 5.

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?

Four sentences, each carrying distinct information: purpose, discovery pattern, auth/behavior, and sibling routing. Front-loaded with the verb and resource. Slightly dense with the topic-list aside wedged mid-paragraph, but no sentence is wasted.

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 must describe returns, and it does (titles, summaries, dates, URLs, plus the embedded topic list). Combined with 100% schema coverage and full annotations, an agent has everything needed to call this 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 baseline is 3, but the description adds real semantic value: it explains that the topic namespace is discoverable from any result's embedded topic list, and that the no-argument call is a valid discovery invocation (0 required params). This meaningfully supplements the schema's 'topic name or part of one' wording.

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?

States a specific verb (List) plus a precisely scoped resource (ClearMind Capital's Clarity Corner education library) and enumerates the returned fields (titles, summaries, dates, URLs) and ordering (newest first). It explicitly distinguishes itself from the sibling search_answers by contrast in ranking strategy.

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 explicit when-to-use ('browse or find recent content'), when-not ('to answer a specific question use search_answers, which ranks by relevance instead of date'), and a concrete call pattern ('call it with no arguments first to see which topics exist'). All routing decisions are spelled out.

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