Skip to main content
Glama
Sign In
shell-use

shell-use

by kyuheon-kr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

exit_scroll_mode

Exit tmux copy-mode to return to normal mode and resume command input after scrolling.

Instructions

Exits tmux copy-mode and returns to normal mode.

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": "<session>"
    },
    "name": "exit_scroll_mode"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of explaining behavior. It accurately discloses the state transition without hidden side effects. However, it does not mention prerequisites (e.g., whether session must be in copy-mode) or error behavior, but for this simple tool the core behavior is transparent.

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 clear sentence with no unnecessary words or repetition. It front-loads the action and is immediately understandable.

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 state-transition tool with an output schema, the description covers the core action but lacks information about the required 'session' parameter and any prerequisite conditions. This makes it minimally viable but not fully complete for an agent to invoke correctly without additional context.

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

Parameters1/5

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

The input schema has one required parameter 'session' with 0% schema description coverage, and the description provides no explanation of what this parameter represents or how to determine its value. This is a significant gap, as the description adds no meaning beyond the parameter's name and type.

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 a specific action ('Exits tmux copy-mode') and the resulting state ('returns to normal mode'). This distinguishes it from sibling tools like scroll or capture, which have different purposes.

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

Usage Guidelines3/5

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

The description implies usage when the user is in tmux copy-mode and wants to return to normal mode, but it does not explicitly state when to use this tool versus alternatives like 'scroll'. There are no exclusions or alternative recommendations, so guidance is only implicit.

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