Brain-MCP

by DDguan2010

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Complete Thought Process

completeThoughtProcess

Finalize and store the conclusion of a thought process in persistent memory for continuous learning and reasoning.

Instructions

Mark a thought process as complete and store the conclusion

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": {
      "chainId": "<chainId>",
      "conclusion": "<conclusion>"
    },
    "name": "completeThoughtProcess"
  }
}

Input Schema

Name	Required	Description	Default
`chainId`	Yes	The thought chain ID
`conclusion`	Yes	Final conclusion of the thought process

Output Schema

Name	Required	Description	Default
`error`	No
`success`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jan 11, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden but lacks behavioral details. It implies a mutation ('Mark as complete and store'), but doesn't disclose permissions needed, whether this is irreversible, what happens to the thought process after completion (e.g., archived or deleted), or any rate limits. The description adds minimal context beyond the basic action.

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?

The description is a single, efficient sentence with zero waste—it directly states the tool's function without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (a mutation with 2 required parameters), no annotations, but a 100% schema coverage and an output schema, the description is minimally adequate. It states the core action but lacks details on behavioral implications, usage context, and output expectations, leaving gaps that could hinder effective agent use.

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%, with clear parameter descriptions in the schema, so the baseline is 3. The description doesn't add meaning beyond the schema—it mentions 'conclusion' but doesn't elaborate on format, length, or content expectations, nor does it explain 'chainId' beyond what the schema provides.

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?

The description clearly states the action ('Mark as complete and store') and the resource ('thought process'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'pauseThinking' or 'resumeThinking' that also manage thought process states, nor does it specify what 'complete' means operationally compared to other terminal states.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., must have an active thought process), exclusions (e.g., cannot complete a paused process), or related tools like 'startThoughtProcess' for initiation or 'getActiveChains' for checking status, leaving usage context unclear.

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