clear_all_trees
Removes all existing thought trees and resets the reasoning state for a fresh start.
Instructions
Clear all trees
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Removes all existing thought trees and resets the reasoning state for a fresh start.
Clear all trees
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description bears full burden. It simply states 'Clear all trees' without disclosing destructive behavior, irreversible consequences, or any other behavioral traits. The agent cannot infer what 'clear' entails.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Extremely concise (3 words) but at the expense of informativeness. The description is too terse to be helpful; it fails to explain what the tool does, leaving the agent with ambiguity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema and no annotations, the description provides minimal context. It does not explain what happens after clearing (e.g., return value, side effects on related data), leaving the tool's behavior opaque.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Input schema has 0 parameters, and baseline is 4 per scoring guidelines. Description adds no parameter info because none is needed, and the schema coverage is 100% by default.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description 'Clear all trees' restates the tool name without additional context, failing to distinguish from sibling tools like 'clear_all' or 'clear_state'. The verb 'clear' is ambiguous regarding scope and side effects.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives. No mention of prerequisites, intended use cases, or conditions under which the tool should be avoided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/HefnySco/agent_mcp_thoughtflow'
If you have feedback or need assistance with the MCP directory API, please join our Discord server