Skip to main content
Glama

status

Retrieve current workspace resolution, kernel PID, busy state, and recent execution details from the IPython workbench to monitor runtime conditions.

Instructions

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

状态范围

还返回当前 IPython 工作台启动时解析的 workspace、其 workspace_resolution 来源类别、Python 解释器、kernel PID、kernel 是否已启动,以及 kernel 是否正忙。 workspace_resolution 只能是 launch_cwd 或explicit_config; 忙碌时 current_execution 是正在运行的正整数执行编号; 空闲时 recent_execution 是最近一次被接受的执行编号。

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

Returns: 当前 IPython 工作台与 kernel 的状态快照。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.13

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the returned fields, the enum-like invariant for workspace_resolution (launch_cwd | explicit_config), and the busy-vs-idle execution-number rule, which is genuinely helpful. It never states explicitly that the call is side-effect free or non-blocking, and the closing 'IPython 通过原生 ZMQ 协议连接,拥有完整能力' line describes the environment rather than this tool's behavior.

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?

It is front-loaded with a clear one-line summary and organized under a 状态范围 heading, but the trailing 'Returns:' sentence repeats the opening sentence verbatim in substance, and the ZMQ 'full capability' note does not earn its place in a status tool's description.

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?

There is no output schema, so the description must describe the return payload and it does enumerate the key fields and their invariants. The remaining gap is that a sibling (execution_status) overlaps in apparent purpose and the description offers no boundary between them, which an agent would need in order to choose correctly.

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 takes zero parameters, so per the baseline this dimension starts at 4. No parameter meaning is required from the description and none is missing.

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 opening sentence names a concrete deliverable (a snapshot of workspace, kernel and recent-execution state) and the body enumerates the specific fields returned: workspace_resolution, Python interpreter, kernel PID, started/busy flags, and current vs recent execution ids. It does not, however, distinguish itself from the sibling execution_status, which on name alone sounds like the same operation.

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?

Usage is only implied: an agent can infer this is the read-only state probe to call before or after run_cell/interrupt/restart, but the description never says when to use it, when not to, or how it relates to execution_status. The current_execution/recent_execution distinction is useful context but is framed as data semantics rather than selection guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.