Skip to main content
Glama
sealablab

Moku MCP Server

by sealablab

list_slots

View configured instrument slots to manage device connections and signal routing for Moku hardware control.

Instructions

List configured instrument slots

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The actual implementation of the list_slots functionality in the MokuMCPServer class, which iterates over instrument slots and queries their configuration.
    async def list_slots(self):
        """
        List configured instrument slots.
    
        Returns:
            {
                "slots": {
                    "1": {"instrument": "CloudCompile", "configured": true},
                    "2": {"instrument": "Oscilloscope", "configured": true},
                    "3": {"configured": false},
                    "4": {"configured": false}
                }
            }
    
        Implementation: See IMPLEMENTATION_GUIDE.md Section 3.8
        """
        if not self.moku_instance:
            return {
                "status": "error",
                "message": "Not connected to any device",
                "suggestion": "Call attach_moku first",
            }
    
        slots = {}
    
        # Query each slot (1-4 for Moku:Go)
        for slot_num in range(1, 5):
            try:
                instrument = self.moku_instance.get_instrument(slot_num)
                if instrument:
                    slots[str(slot_num)] = {
                        "instrument": instrument.__class__.__name__,
                        "configured": True,
                    }
                    logger.debug(f"Slot {slot_num}: {instrument.__class__.__name__}")
                else:
                    slots[str(slot_num)] = {"configured": False}
                    logger.debug(f"Slot {slot_num}: Empty")
            except Exception as e:
                # Slot not configured or error accessing it
                slots[str(slot_num)] = {"configured": False}
                logger.debug(f"Slot {slot_num}: Not configured or error: {e}")
    
        logger.info(f"Slot status: {sum(1 for s in slots.values() if s.get('configured'))} configured")
        return {"slots": slots}
  • The MCP tool definition for list_slots.
    Tool(
        name="list_slots",
        description="List configured instrument slots",
        inputSchema={
            "type": "object",
            "properties": {},
        },
    ),
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 of behavioral disclosure. It fails to indicate whether this is a read-only operation, what data format it returns, or any 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?

The description is extremely terse (4 words) and front-loaded with the verb. While efficient, it borders on under-specification given the lack of annotations or output schema.

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 and no annotations, the description should indicate what the tool returns (e.g., slot identifiers, configurations). Currently insufficient for an agent to understand the operation's value without invoking it.

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 zero parameters and 100% schema coverage of those zero parameters, meeting the baseline of 4. No parameter semantics are needed or provided.

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 uses a clear verb ('List') and specific resource ('configured instrument slots'), distinguishing it from siblings like get_config or discover_mokus. However, it lacks domain context explaining what 'instrument slots' represent in the Moku device system.

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 provided on when to use this tool versus alternatives like get_config or get_device_info, nor any prerequisites or conditions for invocation.

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/sealablab/moku-mcp'

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