Skip to main content
Glama

Reset Project Brain

reset_project_brain

Clears all Project Brain configuration, tasks, and context metadata for a selected project while leaving Git and source code untouched. Use it to reset project state without deleting code.

Instructions

Wipe all Project Brain configuration, tasks, and context metadata inside the selected project. Leaves git and source code untouched.

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

Input Schema

NameRequiredDescriptionDefault
pathNoProject root directory..

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It helpfully discloses what is destroyed (Project Brain configuration, tasks, context metadata) and what is preserved (git and source code untouched). However, it does not state whether the wipe is irreversible, whether confirmation is required, or what the operation returns—important gaps for a destructive tool.

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 destructive action and immediately followed by the preservation guarantee. Every word earns its place with no redundancy.

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?

For a destructive reset tool with no annotations and an output schema covering return values, the description covers the core scope of destruction and preservation. It falls short on irreversibility, confirmation requirements, and differentiation from sibling cleanup tools, leaving meaningful context gaps.

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?

The single parameter 'path' is fully documented in the schema as 'Project root directory,' and the description only adds that it selects the project. No additional meaning (e.g., format, relative vs absolute, default behavior) is provided beyond the schema, so the baseline of 3 applies given 100% schema coverage.

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 uses a specific verb ('Wipe') and enumerates the resources affected ('Project Brain configuration, tasks, and context metadata'), making the tool's purpose unambiguous. It does not, however, distinguish this tool from nearby siblings like reset_context or archive_project_brain, so an agent must infer the difference.

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?

There is no explicit guidance on when to use this tool versus reset_context, archive_project_brain, or other reset/cleanup siblings. The description also omits any prerequisite or warning before invoking a destructive wipe, leaving the agent to infer usage conditions.

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