Skip to main content
Glama

list_instances

View all active Claude instances to monitor AI assistant communication and manage IPC connections.

Instructions

List all active Claude instances

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler for 'list_instances' that sends a 'list' action request to the MessageBroker via BrokerClient and returns the JSON-formatted response.
    elif name == "list_instances":
        response = BrokerClient.send_request({"action": "list"})
        return [TextContent(type="text", text=json.dumps(response, indent=2))]
  • Backend handler for the 'list' action in MessageBroker._process_request() that constructs and returns the list of active instances with their last_seen timestamps from the self.instances dictionary.
    elif action == "list":
        instances = [
            {"id": id, "last_seen": ts.isoformat()}
            for id, ts in self.instances.items()
        ]
        return {"status": "ok", "instances": instances}
  • Registration of the 'list_instances' tool in the MCP server's list_tools() function, including its description and empty input schema (no parameters required).
    Tool(
        name="list_instances",
        description="List all active Claude instances",
        inputSchema={
            "type": "object",
            "properties": {}
        }
    ),
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'List' implies a read operation, it doesn't specify whether this requires authentication, what 'active' means operationally, if there are rate limits, or what format the output takes. The description is minimal and lacks important behavioral context.

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 states exactly what the tool does with zero wasted words. It's appropriately sized for a simple listing tool and front-loads the core functionality.

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?

For a zero-parameter listing tool with no output schema, the description is minimally adequate but lacks important context. It doesn't explain what constitutes an 'active' instance, whether the list is filtered or complete, or what information is returned about each instance. The absence of annotations means more behavioral detail would be helpful.

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?

With 0 parameters and 100% schema description coverage, the baseline is 4. The description appropriately doesn't discuss parameters since none exist, and the schema already fully documents the empty parameter set.

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 active Claude instances'), providing a specific purpose. However, it doesn't differentiate from sibling tools like 'check' or 'auto_process' that might also involve instance operations, so it doesn't fully distinguish from alternatives.

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?

The description provides no guidance on when to use this tool versus alternatives like 'check' or 'register'. It doesn't mention prerequisites, exclusions, or appropriate contexts for listing instances versus other instance-related operations.

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/jdez427/claude-ipc-mcp'

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