Skip to main content
Glama
UserB1ank

interactive-process-mcp

by UserB1ank

list_sessions

List all active interactive process sessions to manage long-running programs such as SSH sessions, REPLs, and installers.

Instructions

List all interactive process sessions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Primary MCP tool handler for list_sessions, registered via @mcp.tool() decorator. Calls SessionManager.list_all() and returns session summaries.
    @mcp.tool()
    def list_sessions() -> dict:
        """List all interactive process sessions."""
        return {"sessions": _mgr.list_all()}
  • The function signature defines the schema: no arguments required, returns a dict with a 'sessions' key.
    def list_sessions() -> dict:
        """List all interactive process sessions."""
        return {"sessions": _mgr.list_all()}
  • Alternative handler for list_sessions in the tools.create_tools() factory. Takes an args dict (ignored) and returns session list.
    def list_sessions(args: dict) -> dict:
        return {"sessions": mgr.list_all()}
  • Registration of list_sessions in the tools tuple list returned by create_tools(). Used by tests to look up the handler.
    ("list_sessions", list_sessions),
  • SessionManager.list_all() helper that returns a list of session info dicts, used by both handler implementations.
    def list_all(self) -> list[dict]:
        with self._lock:
            return [s.info() for s in self._sessions.values()]
Behavior2/5

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

No annotations are present, so the description must cover behavioral traits. It only states the action without revealing whether the operation is read-only, what data is returned, or any side effects, which is insufficient.

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, clear sentence with no superfluous words. It is appropriately sized for the tool's simplicity and front-loads the key information.

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?

Despite having no parameters, the description lacks completeness because it does not explain what constitutes an 'interactive process session' or describe the return format, which is especially important given the absence of an output schema.

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?

There are no parameters, so schema coverage is 100%. The description does not need to add meaning beyond the schema, meeting the baseline expectation for zero-parameter tools.

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

Purpose5/5

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

Description specifies a clear verb ('list') and a distinct resource ('interactive process sessions'). It is unambiguous and differentiates from siblings like 'get_session_info' which targets a single session.

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 usage guidance is provided. The description does not mention when to use this tool versus alternatives like 'get_session_info' or the other session-related tools, leaving the agent to infer context.

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/UserB1ank/interactive-process-mcp'

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