Skip to main content
Glama
raghavharness

remote-shell-mcp

remote_pane_next

Switch to the next pane in the active remote shell session, facilitating quick navigation between terminal panes.

Instructions

Switch to the next pane in the session.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionIdNoSession ID (defaults to active)
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 only states 'Switch to the next pane' without explaining whether it changes focus, wraps around, or handles inactive sessions. No side effects or error conditions are disclosed.

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, front-loaded sentence with no wasted words. It efficiently communicates the core action without elaborating unnecessarily.

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?

For a simple one-parameter tool, the description is minimally adequate. However, given the extensive set of sibling pane tools, it lacks context on how 'next' relates to pane ordering and how this differs from focus or list operations, making it only partially complete.

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

Parameters3/5

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

The input schema fully describes the only parameter (sessionId) with a note about defaulting to the active session. Since schema coverage is 100%, the description adds no additional meaning, and baseline 3 is appropriate.

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 uses a specific verb 'Switch' and names the resource 'next pane in the session', clearly indicating a navigation action. However, it does not explicitly distinguish from sibling tools like remote_pane_focus or remote_pane_list, though the 'next' qualifier implies a sequence.

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?

There is no guidance on when to use this tool versus alternatives such as remote_pane_focus or remote_pane_list. No prerequisites, scenarios, or exclusions are mentioned.

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/raghavharness/remote-shell-mcp'

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