Skip to main content
Glama
Sign In
mcp-interactive-terminal

mcp-interactive-terminal

by hugo94z
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

terminal_resize

Set a pseudo-terminal session's width and height to correct text wrapping and support full-screen programs. Requires session_id, cols, and rows.

Instructions

Resize the pseudo-terminal (affects wrapping and full-screen programs).

Args: session_id: Session returned by terminal_start. cols: New width, 2..1000. rows: New height, 2..500.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "session_id": "<session_id>",
      "cols": "<cols>",
      "rows": "<rows>"
    },
    "name": "terminal_resize"
  }
}

Input Schema

NameRequiredDescriptionDefault
colsYes
rowsYes
session_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Since no annotations are provided, the description carries the full behavioral burden. It discloses the tool's effect on the environment (wrapping and full-screen programs) and provides critical operational constraints—the strict minimum and maximum range limits for cols (2..1000) and rows (2..500), which define acceptable input behavior.

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 definition is highly efficient. It begins with a clear summary, followed immediately by an easy-to-parse argument list that integrates both semantic meaning and functional constraints without unnecessary padding.

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?

The definition is exceptionally complete for a tool with no output schema or annotations. It provides the required inputs, the operational constraints for those inputs, and the necessary linkage to the terminal session lifecycle.

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

Parameters5/5

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

The schema coverage is noted as 0%, meaning the description must compensate heavily. The description excels by defining the unit (width/height) and providing explicit bounds for both `cols` and `rows`, which is critical semantic and validation information absent from the bare input schema.

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 the action (Resize) and the resource (pseudo-terminal). It provides specific functional consequences (affects wrapping and full-screen programs), clearly distinguishing its purpose from sibling tools like terminal_start or terminal_exec.

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?

It provides an essential prerequisite condition by stating that the required session_id must be 'Session returned by terminal_start.' This guides the agent on the correct workflow and dependency, although it does not explicitly state when *not* to use it.

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