loommux
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOOMMUX_MONITOR_URL | No | Override the monitor event-ingest URL. | |
| LOOMMUX_MONITOR_DISABLED | No | Set to 1 to disable monitor publishing. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| run_cellA | 向持久 IPython kernel 提交一个原始 IPython cell。 请你使用 IPython 的思想来优雅使用本系列工具。 输入接受一段 loommux IPython cell 源码。普通 Python 文本使用默认策略;若作者
需要声明本次 cell 的观察策略,使用位于物理行首的 等待上限本次调用默认最多等待 10 秒。
完整输出若任一有效
图像展示IPython 执行编号与后续操作每个已接受的提交都会获得一个连续递增的正整数 |
| statusB | 返回 workspace、kernel 与最近执行记录的观察状态。 状态范围返回当前 IPython 工作台启动时解析的 workspace、其
.. code-block:: text IPython 通过原生 ZMQ 协议连接,拥有完整能力。 Returns: 当前 IPython 工作台与 kernel 的状态快照。 |
| execution_statusA | 返回一个 execution 的状态与元数据,不返回完整输出正文。 选择规则提供 |
| read_outputB | 读取一个 execution 的指定输出流。 选择与流
行坐标
完整读取调用者已确定需要完整消费所选流时,省略 |
| search_outputA | 在一个 execution 的指定输出流中搜索文本或正则表达式。 选择与匹配
命中上下文每条命中保留原始所选流行号,并以 |
| waitA | 等待一个 execution 结束,或在指定时限到达时返回其当前状态。 选择与等待
完整输出交付当所选 execution 的原始 |
| interruptA | 向当前正在运行的 execution 发送 kernel 中断信号。 中断语义该工具只作用于当前 running 记录。信号已发送不等同于记录已终态:
kernel 到达 IOPub Returns:
已发送信号时返回目标 |
| restartA | 重启 IPython kernel,并保留当前持久 IPython 会话的 execution 历史。 重置边界若存在 running execution,它会先标记为 Returns: 新 kernel 的状态与 PID;重启失败时返回 workspace 或 kernel 启动错误。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool has a distinct role in the IPython execution lifecycle: submit, wait, interrupt, restart, global status, per-execution status, read, and search. The only real ambiguity is between status and execution_status, which are easy to confuse by name even though one is a workspace/kernel snapshot and the other is per-execution.
Names are all lowercase snake_case and group logically: action tools are imperative verbs (run_cell, wait, interrupt, restart) and retrieval/query tools are noun or verb_noun forms (status, execution_status, read_output, search_output). The mix of bare verbs and noun-only status names is a minor deviation from a strict verb_noun pattern but remains predictable.
Eight tools is well-scoped for a persistent IPython kernel server: submission, lifecycle control, and output retrieval each have dedicated tools without redundancy. No tool feels superfluous.
The core lifecycle is covered: run, wait, interrupt, restart, status, and output reading/searching. A minor gap is the lack of a way to list or enumerate past executions beyond the most recent one, which agents must track themselves.