Skip to main content
Glama
QiuwenZheng

interminal

by QiuwenZheng
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

list_sessions

Read-only

Retrieve a list of all active SSH and local terminal sessions, including session IDs and connection details, to discover or resume existing sessions.

Instructions

List all active terminal sessions (SSH and local) managed by this server.

USAGE: Call this to discover or resume existing session_ids. Skip it if you
already hold the session_id you need. To create a session use create_local
or connect_ssh; to close one use disconnect.

Returns a list of dicts, each with:
    - session_id: the session's identifier.
    - type: 'ssh' or 'local'.
    - host, port: the remote endpoint (SSH only).
    - shell: the shell executable (local only).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.7/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint: true. The description adds details about the return format (list of dicts with specific fields), enhancing transparency beyond annotations.

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?

Very concise: a brief summary, usage guidelines, and return format. No redundant sentences. Front-loaded for quick understanding.

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

Completeness5/5

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

Given no parameters, an output schema exists, and annotations cover readOnlyHint, the description provides complete context: purpose, usage, and return fields.

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?

No parameters exist, so schema coverage is 100%. The description adds value by explaining the return structure, which is beyond baseline.

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 clearly states it lists all active terminal sessions (SSH and local). It distinguishes from siblings by referencing create_local and connect_ssh for creation and disconnect for closing.

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

Usage Guidelines5/5

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

Explicitly states when to use (discover/resume session_ids) and when not to (if you already have the ID). Also provides alternatives for creation and closing.

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/QiuwenZheng/interminal'

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