Skip to main content
Glama
MichengLiang

loommux

by MichengLiang
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

python_status

Retrieve workspace resolution, kernel PID, running status, and recent execution number to diagnose the Python execution environment.

Instructions

返回 workspace、kernel 与最近执行记录的观察状态。

状态范围

返回 server 启动时解析的 workspace、其 workspace_resolution 来源 类别、Python 解释器、kernel PID、kernel 是否已启动，以及 kernel 是否 正忙。workspace_resolution 只能是 launch_cwd 或 explicit_config；它不公开 resolver 的路径或内容，也不公开 kernel session 的 private runtime root。忙碌时 current_execution 是正在 运行的正整数执行编号；空闲时 recent_execution 是最近一次被接受的 执行编号。kernel-local execution count 只用于诊断，不能用来选择 loommux execution。

.. code-block:: text

可见标签 In [N]
        =
loommux execution N
        !=
IPython kernel-local execution_count

IPython 通过原生 ZMQ 协议连接，拥有完整能力。

Returns: 当前 server 与 kernel 的状态快照。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A4/5.0
Behavior4/5

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

With no annotations, the description carries full burden and discloses important behavioral details: workspace_resolution limits, non-exposure of private runtime, diagnostic-only execution counts, and IPython ZMQ capabilities.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is structured but somewhat verbose, including an ASCII art code block that may not be essential. The key information is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and 0 parameters, the description is comprehensive, covering all returned fields, limitations, and the IPython connection. It is complete for a status tool.

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, so baseline is 4. The description does not need to add meaning beyond the schema, which is empty.

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?

The description explicitly states it returns the observation status of workspace, kernel, and recent execution. It lists specific fields and distinguishes itself from other tools by its broad scope (workspace + kernel + execution).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not explicitly state when to use this tool versus alternatives like `python_execution_status`. Usage is implied by its purpose, but no explicit guidance or conditions are provided.

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/MichengLiang/loommux'

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