Skip to main content
Glama
heresun

OrbStack MCP Server

by heresun

orbstack_stop

Idempotent

Stop all running Docker containers and Linux virtual machines managed by OrbStack on macOS. Use this tool to halt active services and free system resources.

Instructions

停止 OrbStack 服务。

这将停止所有运行中的容器和 Linux 机器。

Returns: str: 停止结果

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the `orbstack_stop` tool, which executes the `orb stop` command.
    async def orbstack_stop() -> str:
        """停止 OrbStack 服务。
    
        这将停止所有运行中的容器和 Linux 机器。
    
        Returns:
            str: 停止结果
        """
        code, stdout, stderr = await _run_orb(["stop"])
        if code != 0:
            return _format_error(stderr)
        return "OrbStack 已停止" + (f"\n{stdout}" if stdout else "")
  • Registration of the `orbstack_stop` tool using the @mcp.tool decorator.
    @mcp.tool(
        name="orbstack_stop",
        annotations={
            "title": "停止 OrbStack",
            "readOnlyHint": False,
            "destructiveHint": False,
            "idempotentHint": True,
            "openWorldHint": False,
        },
Behavior3/5

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

The description adds valuable context beyond annotations by stating '这将停止所有运行中的容器和 Linux 机器' (This will stop all running containers and Linux machines), which clarifies the scope and impact of the operation. Annotations already indicate it's not read-only (readOnlyHint: false), idempotent (idempotentHint: true), and non-destructive (destructiveHint: false), so the description doesn't contradict these but provides additional behavioral detail about what gets affected.

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 extremely concise and front-loaded: the first sentence states the core purpose, the second adds crucial behavioral context, and the third specifies the return type. Every sentence earns its place with no wasted words or redundancy.

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

Completeness4/5

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

Given that the tool has 0 parameters, annotations cover safety aspects (idempotent, non-destructive), and there's an output schema (implied by 'Returns: str'), the description is reasonably complete. It explains what the tool does and its scope, though it could benefit from more usage guidance relative to siblings.

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?

The tool has 0 parameters, and schema description coverage is 100%, so there's no need for parameter documentation in the description. The baseline for 0 parameters is 4, as the description appropriately doesn't discuss parameters that don't exist.

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 ('停止' meaning 'stop') and the target ('OrbStack 服务' meaning 'OrbStack service'), which is a specific verb+resource combination. However, it doesn't explicitly distinguish this tool from sibling tools like 'orbstack_docker_stop' or 'orbstack_machine_stop', which appear to stop specific components rather than the entire service.

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. It doesn't mention when this tool is appropriate (e.g., for stopping the entire OrbStack environment) versus using more specific stop tools for containers or machines, nor does it discuss prerequisites or exclusions.

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/heresun/orbstack-mcp'

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