Skip to main content
Glama

magg_list_kits

Retrieve a list of available kits and their current status to streamline server management and tool configuration within the MAGG MCP ecosystem.

Instructions

List all available kits with their status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorsNo
outputNo

Implementation Reference

  • Handler function for the 'magg_list_kits' tool in ServerManager. Calls kit_manager.list_all_kits() and formats the response with summary statistics.
    async def list_kits(self) -> MaggResponse:
        """List all available kits with their status."""
        try:
            kits = self.kit_manager.list_all_kits()
    
            return MaggResponse.success({
                "kits": kits,
                "summary": {
                    "total": len(kits),
                    "loaded": len([k for k in kits.values() if k['loaded']]),
                    "available": len([k for k in kits.values() if not k['loaded']])
                }
            })
    
        except Exception as e:
            return MaggResponse.error(f"Failed to list kits: {str(e)}")
  • Registration of the 'magg_list_kits' tool (as part of kit tools) in MaggServer._register_tools method using self.mcp.tool().
    (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),
  • KitManager.list_all_kits(): Discovers all available kits from kit.d directories, combines with loaded kits, loads metadata for available kits, and returns detailed status for each.
    def list_all_kits(self) -> dict[str, dict[str, Any]]:
        """List all available kits with their status.
    
        Returns:
            Dict mapping kit names to their info (loaded, path, description, servers)
        """
        available_kits = self.discover_kits()
        loaded_kits = self.kits
    
        result = {}
    
        for kit_name, kit_config in loaded_kits.items():
            result[kit_name] = {
                'loaded': True,
                'path': str(available_kits.get(kit_name, 'unknown')),
                'description': kit_config.description,
                'author': kit_config.author,
                'version': kit_config.version,
                'keywords': kit_config.keywords,
                'servers': list(kit_config.servers.keys())
            }
    
        for kit_name, kit_path in available_kits.items():
            if kit_name not in result:
                kit_config = self.load_kit(kit_path)
                if kit_config:
                    result[kit_name] = {
                        'loaded': False,
                        'path': str(kit_path),
                        'description': kit_config.description,
                        'author': kit_config.author,
                        'version': kit_config.version,
                        'keywords': kit_config.keywords,
                        'servers': list(kit_config.servers.keys())
                    }
                else:
                    result[kit_name] = {
                        'loaded': False,
                        'path': str(kit_path),
                        'description': 'Failed to load kit metadata',
                        'author': None,
                        'version': None,
                        'keywords': [],
                        'servers': []
                    }
    
        return result
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states it's a list operation, implying read-only behavior, but doesn't disclose any behavioral traits such as pagination, rate limits, authentication needs, or what 'status' entails (e.g., loaded, available, error states). The description is minimal and lacks context beyond the basic action.

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, efficient sentence that front-loads the core action ('List all available kits') and adds value with 'with their status'. There is zero waste or redundancy, making it appropriately sized for a simple list tool.

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's simplicity (0 parameters, output schema exists), the description is minimally adequate. It states what the tool does but lacks behavioral context (e.g., how status is defined, any limitations). With no annotations and an output schema, the description could benefit from more detail on the 'status' aspect or usage scenarios, but it meets the basic requirement for a list operation.

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?

The tool has 0 parameters, and schema description coverage is 100% (empty schema). The description doesn't need to add parameter details, and it appropriately doesn't mention any. Baseline for 0 parameters is 4, as there's no parameter burden to compensate for.

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 clearly states the verb ('List') and resource ('all available kits') with the additional detail 'with their status', which specifies what information is returned. It distinguishes from siblings like 'magg_kit_info' (likely detailed info on a specific kit) and 'magg_load_kit'/'magg_unload_kit' (mutations), but doesn't explicitly differentiate from other list operations like 'magg_list_servers'.

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. The description doesn't mention prerequisites, when it's appropriate (e.g., for inventory checks vs. operational decisions), or contrast with siblings like 'magg_search_servers' for filtered queries. Usage is implied by the action 'list all', but no explicit context or exclusions are stated.

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