Skip to main content
Glama
rishabkoul
by rishabkoul

list-terminals

Retrieve a list of all active iTerm2 terminal sessions with their current information and status for session management.

Instructions

List all active terminals and their information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'list-terminals' tool. It retrieves active terminals from the global 'terminals' Map, computes the count and list of IDs, and returns a formatted text response with this information.
    async () => {
      const activeTerminals = Array.from(terminals.entries()).map(([id]) => id);
      const count = terminals.size;
    
      return {
        content: [
          {
            type: "text",
            text: `Number of active terminals: ${count}\nActive terminal IDs: ${
              activeTerminals.join(", ") || "None"
            }`,
          },
        ],
      };
    }
  • index.js:243-262 (registration)
    Registration of the 'list-terminals' tool with McpServer.tool(). Includes name, description, empty schema, and inline handler function.
    server.tool(
      "list-terminals",
      "List all active terminals and their information",
      {},
      async () => {
        const activeTerminals = Array.from(terminals.entries()).map(([id]) => id);
        const count = terminals.size;
    
        return {
          content: [
            {
              type: "text",
              text: `Number of active terminals: ${count}\nActive terminal IDs: ${
                activeTerminals.join(", ") || "None"
              }`,
            },
          ],
        };
      }
    );
  • Global Map storing active terminals, used by the 'list-terminals' handler to list them.
    const terminals = new Map();
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool lists active terminals but doesn't clarify what 'active' means, whether it requires permissions, how the information is formatted, or if there are rate limits. This leaves significant gaps in understanding the tool's behavior beyond the basic action.

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?

The description is a single, efficient sentence that front-loads the core action and resource without any wasted words. It's appropriately sized for a simple tool with no parameters, making it easy to parse and understand quickly.

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?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate but lacks depth. It doesn't explain what 'information' includes or the return format, which could be important for an agent to use the tool effectively. However, for a basic list operation, it meets the minimum viable threshold.

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?

With 0 parameters and 100% schema description coverage, the input schema fully documents the lack of parameters. The description adds no parameter-specific information, which is acceptable here since there are no parameters to explain. A baseline of 4 is appropriate as the schema handles the parameter semantics completely.

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 description clearly states the action ('List') and target resource ('all active terminals and their information'), making the purpose immediately understandable. It doesn't differentiate from sibling tools like 'close-terminal' or 'open-terminal', which would require explicit comparison, but it's specific enough to convey the tool's function without being tautological.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'open-terminal' or 'read-output'. It lacks context about prerequisites, such as whether terminals need to be active first, or any exclusions, leaving the agent to infer usage from the tool name alone.

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/rishabkoul/iTerm-MCP-Server'

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