Skip to main content
Glama

asset_root_enroll

Enroll a Claude Code config folder so its instructions, skills, agents and commands are backed up automatically at session boundaries and on every write, or stop backing it up while keeping stored copies.

Instructions

Enroll a Claude Code config folder into the workflow backup, or stop backing it up.

Enrolling backs the folder up at once and then on every session boundary and file write. Only the user's assets are read (instructions, project memory, skills, agents, commands, hook scripts and registrations, MCP definitions without secrets, plugin lists); credentials, caches and OS's own files never are. Ignoring stops the backup and keeps everything already stored. Only this session's Claude Code config folder (or one OS installed into) can be enrolled; macOS only.

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

Input Schema

NameRequiredDescriptionDefault
pathNoAbsolute path of the config folder; empty means this session's folder
actionNo"enroll" (default) or "ignore"enroll
profileNoProfile name shared by folders that copy one another, e.g. "main"; needed on first enroll
categoriesNoComma-separated categories to back up; empty means the defaults

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.1

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden and does so well. It discloses backup timing (immediately, then on session boundaries and file writes), read scope (only user assets, never credentials/caches/OS files), data retention on ignore, platform restriction (macOS only), and eligible path constraints.

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 front-loaded with the core action and consequence, then adds only relevant behavioral details. Every sentence contributes useful scope, timing, retention, or platform information without redundancy.

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 the lack of annotations and the presence of an output schema, the description is largely complete: it covers safety-relevant read scope, backup timing, ignore behavior, platform, and path eligibility. Minor gaps remain around idempotency, profile behavior, and why this tool is preferable to backup siblings in specific situations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents all four parameters in detail. The description adds meaningful constraints beyond the schema, notably that only this session's config folder or an OS-installed folder can be enrolled and that this is macOS only, though it does not further explain profile or categories.

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 states a specific verb and resource: enrolling a Claude Code config folder into workflow backup, or stopping that backup. It is clear without opening the schema, though it does not explicitly differentiate itself from sibling backup tools such as asset_backup_run or asset_backup_status.

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?

The description gives clear usage context: use enroll to start backing up a folder and ignore to stop backing it up while retaining stored data. It does not explicitly name alternatives or exclusions relative to sibling backup tools, so guidance is strong but not complete.

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

Deploy Server

Other Tools