Skip to main content
Glama

Archive Project Brain

archive_project_brain

Archive current Project Brain settings and context files to .project_brain_archive/ before a reset or pivot, preserving project history.

Instructions

Archive current Project Brain settings and context files to .project_brain_archive/ before a reset or pivot, preserving history.

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": "archive_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

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden; it does disclose the write destination (.project_brain_archive/) and that history is preserved, which is the key fact for a mutation. It is silent on whether an existing archive is overwritten, appended to, or versioned, and on whether files move versus copy — real risks for a tool that touches user data.

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?

One sentence, front-loaded with the action and the artifact, then the destination, then the trigger condition, then the guarantee. No filler or restatement of the title beyond what adds information.

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?

Given a single defaulted parameter and an output schema that covers return values, the description supplies what is actually needed: what gets archived, where it goes, and when to do it. The only material omission is collision behavior when the archive directory already exists.

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?

There is a single parameter whose schema description is fully covered ('Project root directory.' with default '.'), so the schema already does the work. The description adds no meaning about how path affects the archive location, which is the one thing an agent might misjudge (e.g., whether the archive lands inside or outside the given root).

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 gives a specific verb (archive) plus the resource (Project Brain settings and context files) and the exact destination (.project_brain_archive/), so an agent knows precisely what is produced. It stops short of naming the sibling it pairs with (reset_project_brain) as an explicit counterpart, so differentiation from that tool is only implied.

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

Usage Guidelines4/5

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

It states a clear trigger condition: run this 'before a reset or pivot,' which directly scopes it against the destructive reset path. It does not spell out when archiving is unnecessary or what to do if an archive already exists, so the guidance is contextual rather than exhaustive.

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