Skip to main content
Glama
Sign In
clu

clu

by QiandingHuang666
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

session_list

Read-onlyIdempotent

Lists tmux-managed sessions created by alloc preemption so you can inspect active resource sessions; use exec for ordinary query tasks instead.

Instructions

列出 tmux 托管会话（仅 alloc 抢占产生的资源会话；普通查询任务请用 exec）。

要求远端装有 tmux；机器上没有 tmux 时列表为空或 alloc 会明确报错。

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": "session_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
connectionNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds genuinely new behavioral facts: the listing only surfaces alloc-created resource sessions, and without tmux the result is an empty list or an explicit error from alloc.

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?

Two short sentences with no filler: the scope restriction is front-loaded in the first, the environment prerequisite and failure mode in the second. Every clause carries information an agent needs.

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?

Return shape is covered by the output schema and the tmux dependency is disclosed, but the one input parameter remains entirely undocumented across both schema and description. Adequate for calling the tool with no arguments, incomplete for anyone who needs to target a specific connection.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single 'connection' parameter has 0% schema description coverage, and the description never explains what it accepts or how a null default resolves (presumably the default remote). With low coverage the description is expected to compensate, and it does not.

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?

States a specific verb and resource (list tmux-managed sessions) and narrows scope to resource sessions produced by alloc, explicitly ruling out general queries. An agent can distinguish it from exec and the other session_* siblings without opening any schema.

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

Usage Guidelines4/5

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

Gives an explicit routing rule — ordinary query tasks should use exec — plus the prerequisite that tmux must be installed on the remote. It does not explain how this relates to session_info, session_start, or session_release, so the alternative coverage is partial rather than exhaustive.

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

Deploy Server

Other Tools