Skip to main content
Glama
JeremyLakeyJr

Friday MCP Server

deactivate_skill

Deactivates an installed skill by its ID, disabling its functionality without removing it.

Instructions

Deactivate an installed skill.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skill_idYes

Implementation Reference

  • The core implementation of deactivate_skill in SkillStore. Delegates to _set_active_state with active=False.
    def deactivate_skill(self, skill_id: str) -> dict[str, Any]:
        return self._set_active_state(skill_id, False)
  • Private helper used by deactivate_skill to update the 'active' flag in the registry for a given skill_id.
    def _set_active_state(self, skill_id: str, active: bool) -> dict[str, Any]:
        registry = self._load_registry()
        record = registry.get(skill_id)
        if record is None:
            raise SkillError(f"Unknown skill '{skill_id}'.")
        record["active"] = active
        registry[skill_id] = record
        self._save_registry(registry)
        return record
  • The MCP tool handler function for 'deactivate_skill'. It is a thin wrapper calling SkillStore.deactivate_skill.
    @mcp.tool()
    def deactivate_skill(skill_id: str) -> dict:
        """Deactivate an installed skill."""
        return skill_store.deactivate_skill(skill_id)
  • The @mcp.tool() decorator registers deactivate_skill as an MCP tool in the skills module.
    @mcp.tool()
    def activate_skill(skill_id: str) -> dict:
        """Activate an installed skill."""
        return skill_store.activate_skill(skill_id)
    
    @mcp.tool()
  • Top-level registration entry point that calls skills.register() which in turn registers deactivate_skill.
    def register_all_tools(mcp, *, config, skill_store) -> None:
        system.register(mcp, config=config)
        utils.register(mcp)
        web.register(mcp, config=config)
        workspace.register(mcp, config=config)
        skills.register(mcp, skill_store=skill_store)
Behavior2/5

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

No annotations are provided, and the description gives no behavioral details beyond the action itself. It does not disclose whether deactivation affects other skills, requires permissions, or has side effects.

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?

Single sentence, no unnecessary words. However, it may be too brief to be fully informative, but conciseness is not penalized for brevity alone.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, no annotations, and a single parameter, the description fails to explain return values, error conditions, or post-conditions. It leaves significant gaps for an AI agent.

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 coverage is 0%, and the description does not explain the 'skill_id' parameter (e.g., format, valid values, or purpose). The description adds no meaning beyond the schema.

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?

Description clearly states verb 'Deactivate' and resource 'skill', indicating a specific action on an installed skill. However, it does not differentiate from sibling tools like 'remove_skill' or '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., 'remove_skill' or 'activate_skill'). The description provides no context for appropriate usage scenarios.

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