Skip to main content
Glama
JeremyLakeyJr

Friday MCP Server

remove_skill

Remove a skill from Friday MCP Server while automatically preserving a rollback backup for recovery.

Instructions

Remove a skill and keep a rollback backup.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skill_idYes

Implementation Reference

  • The MCP tool handler for 'remove_skill'. Decorated with @mcp.tool(), it delegates to skill_store.remove_skill().
    @mcp.tool()
    def remove_skill(skill_id: str) -> dict:
        """Remove a skill and keep a rollback backup."""
        return skill_store.remove_skill(skill_id)
  • The core business logic for remove_skill. Loads the registry, validates the skill exists, moves the file to a timestamped backup, removes the registry entry, and returns removal status with backup path.
    def remove_skill(self, skill_id: str) -> dict[str, Any]:
        registry = self._load_registry()
        record = registry.get(skill_id)
        if record is None:
            raise SkillError(f"Unknown skill '{skill_id}'.")
    
        skill_path = Path(record["path"])
        removed = skill_path.exists()
        if removed:
            timestamp = self._timestamp_slug()
            backup_path = self.backups_dir / f"{skill_id}-{timestamp}.md"
            shutil.move(str(skill_path), backup_path)
            record["backup_path"] = str(backup_path)
    
        registry.pop(skill_id)
        self._save_registry(registry)
        return {
            "removed": removed,
            "skill_id": skill_id,
            "backup_path": record.get("backup_path"),
        }
  • The 'register' function in skills.py registers all skill tools including remove_skill via the @mcp.tool() decorator on line 63.
    def register(mcp, *, skill_store) -> None:
        @mcp.tool()
  • The register_all_tools function calls skills.register(mcp, skill_store=skill_store), which registers all skill tools including remove_skill.
    skills.register(mcp, skill_store=skill_store)
  • The _timestamp_slug helper used to generate unique backup filenames (e.g., 'my-skill-20250101T120000Z.md').
    def _timestamp_slug(self) -> str:
        return datetime.now(UTC).strftime("%Y%m%dT%H%M%SZ")
Behavior3/5

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

Without annotations, the description carries full burden. It discloses the backup behavior but omits other traits like required permissions, irreversibility (despite backup), and effects on dependent data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the action and key behavior. No unnecessary words, though it could be slightly expanded for clarity.

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?

The description partially covers the tool's behavior (backup) but lacks details on return values, error handling, and side effects. With no output schema, more context would be beneficial.

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

Parameters2/5

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

Schema description coverage is 0% and the description does not explain the skill_id parameter (e.g., format, where to find it). It adds no value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Remove' and the resource 'skill', and adds 'keep a rollback backup' to differentiate from sibling tools like deactivate_skill and rollback_skill.

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 on when to use this tool versus alternatives (e.g., deactivate_skill for temporary disable, rollback_skill for reverting). No prerequisites or exclusions mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/JeremyLakeyJr/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server