Skip to main content
Glama

magg_enable_server

Activate a specified server in the MAGG MCP system by providing its name, enabling it for immediate use and integration with MAGG's aggregated server capabilities.

Instructions

Enable a server.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesServer name to enable

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorsNo
outputNo

Implementation Reference

  • The handler function that implements the magg_enable_server tool. Enables the specified server by updating its enabled status in the configuration, saving the config, and mounting the server.
    async def enable_server(
        self,
        name: Annotated[str, Field(description="Server name to enable")],
    ) -> MaggResponse:
        """Enable a server."""
        try:
            config = self.config
    
            if name not in config.servers:
                return MaggResponse.error(f"Server '{name}' not found")
    
            server = config.servers[name]
    
            if server.enabled:
                return MaggResponse.error(f"Server '{name}' is already enabled")
    
            server.enabled = True
    
            if not self.save_config(config):
                return MaggResponse.error(f"Failed to save configuration for server '{name}'")
    
            success = await self.server_manager.mount_server(server)
    
            return MaggResponse.success({
                "action": "server_enabled",
                "server": {"name": name},
                "mounted": success
            })
    
        except Exception as e:
            return MaggResponse.error(f"Failed to enable server: {str(e)}")
  • Registers the enable_server method as the 'magg_enable_server' tool (via self_prefix_) in the list of tools and applies the FastMCP tool decorator with a response wrapper.
    def _register_tools(self):
        """Register all Magg management tools programmatically.
        """
        self_prefix_ = self.self_prefix_
    
        tools = [
            (self.add_server, f"{self_prefix_}add_server", None),
            (self.remove_server, f"{self_prefix_}remove_server", None),
            (self.list_servers, f"{self_prefix_}list_servers", None),
            (self.enable_server, f"{self_prefix_}enable_server", None),
            (self.disable_server, f"{self_prefix_}disable_server", None),
            (self.search_servers, f"{self_prefix_}search_servers", None),
            (self.smart_configure, f"{self_prefix_}smart_configure", None),
            (self.analyze_servers, f"{self_prefix_}analyze_servers", None),
            (self.status, f"{self_prefix_}status", None),
            (self.check, f"{self_prefix_}check", None),
            (self.reload_config_tool, f"{self_prefix_}reload_config", None),
            (self.load_kit, f"{self_prefix_}load_kit", None),
            (self.unload_kit, f"{self_prefix_}unload_kit", None),
            (self.list_kits, f"{self_prefix_}list_kits", None),
            (self.kit_info, f"{self_prefix_}kit_info", None),
        ]
    
        def call_tool_wrapper(func):
            @wraps(func)
            async def wrapper(*args, **kwds):
                result = await func(*args, **kwds)
    
                if isinstance(result, MaggResponse):
                    return result.as_json_text_content
    
                return result
    
            return wrapper
    
        for method, tool_name, options in tools:
            self.mcp.tool(name=tool_name, **(options or {}))(call_tool_wrapper(method))
    
        self._register_resources()
        self._register_prompts()
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It states the action but doesn't reveal critical traits: whether this requires admin permissions, if it's idempotent, what happens on success/failure, or side effects (e.g., starting services). This leaves significant gaps for a mutation 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?

The description is a single, direct sentence with zero waste: 'Enable a server.' It's front-loaded and appropriately sized for the simple action, earning full marks for efficiency.

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?

Given the tool has an output schema (which handles return values) and high schema coverage, the description's minimalism is somewhat acceptable. However, as a mutation tool with no annotations, it should provide more context on behavior and usage to be fully complete, leaving room for improvement.

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?

Schema description coverage is 100%, with the parameter 'name' clearly documented as 'Server name to enable'. The description adds no additional meaning beyond this, such as format constraints or examples. Since the schema does the heavy lifting, the baseline score of 3 is appropriate.

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

Purpose3/5

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

The description states the action ('enable') and resource ('a server'), which provides a basic understanding of purpose. However, it lacks specificity about what 'enable' means operationally and doesn't differentiate from sibling tools like 'magg_disable_server' beyond the obvious opposite action. This makes it vague rather than clearly distinct.

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 is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., server must exist or be disabled), exclusions, or relationships with siblings like 'magg_disable_server' or 'magg_add_server'. The agent must infer usage from context alone.

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

Related 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/sitbon/magg'

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