Skip to main content
Glama

cachly — Explain it once. Every AI knows it.

brain_doctor

Check the health of your AI Brain and get actionable recommendations. Reports: lesson count, context entries, last session age, open failures, quality score, effective IQ boost, stale index. Returns a prioritized list of issues with fix instructions.

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

Input Schema

NameRequiredDescriptionDefault
instance_idNoUUID of the cache instance.
workspace_pathNoAbsolute path to workspace root — enables package.json analysis for openclaw cross-promo (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does well on output disclosure (enumerated metrics, prioritized issue list with fix instructions), which tells the agent what a call yields. It never states that the operation is non-mutating/read-only, nor any cost, latency, or permission characteristics — gaps that matter for a tool with zero annotation coverage.

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?

Two sentences, front-loaded with the core action, followed by a compact enumeration of reported fields. No filler, no repetition of the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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, listing the seven metrics and the shape of the result (prioritized issues plus fix instructions). What's missing is enough detail to set expectations about default scoping when instance_id/workspace_path are omitted, and confirmation that the call makes no changes.

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 description coverage is 100%, so both optional parameters (instance_id, workspace_path) are already documented, including the package.json cross-promo caveat for workspace_path. The description adds nothing about either parameter or about behavior when they are omitted. Baseline 3 applies since the schema does all the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Check the health of your AI Brain') and enumerates exactly what the report covers — lesson count, context entries, session age, open failures, quality score, IQ boost, stale index. That enumeration makes the tool's scope unambiguous. It stops short of naming how it differs from sibling diagnostics like brain_predict or brain_search, so it lands at 4 rather than 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied via the phrase 'get actionable recommendations' — an agent can infer this is the post-setup or troubleshooting entry point. There is no explicit when-to-use, no when-not-to-use, and no named alternative among the many brain_* siblings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.