Skip to main content
Glama
heresun

OrbStack MCP Server

by heresun

orbstack_compose_down

Idempotent

Stop and remove Docker Compose services to free system resources. Specify a project directory to manage container lifecycle.

Instructions

使用 Docker Compose 停止并移除服务。

Args: params: 包含项目目录

Returns: str: 停止结果

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function 'orbstack_compose_down' that executes 'docker compose down' for a given project directory.
    async def orbstack_compose_down(params: DockerComposeInput) -> str:
        """使用 Docker Compose 停止并移除服务。
    
        Args:
            params: 包含项目目录
    
        Returns:
            str: 停止结果
        """
        args = ["compose", "-f", f"{params.project_dir}/docker-compose.yml", "down"]
    
        code, stdout, stderr = await _run_docker(args, timeout=120)
        if code != 0:
            return _format_error(stderr)
        return f"Compose 项目已停止\n{stdout or stderr}"
  • MCP tool registration for 'orbstack_compose_down'.
    @mcp.tool(
        name="orbstack_compose_down",
        annotations={
            "title": "停止 Compose 项目",
            "readOnlyHint": False,
            "destructiveHint": False,
            "idempotentHint": True,
            "openWorldHint": False,
        },
    )
Behavior3/5

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

Annotations provide significant behavioral information: readOnlyHint=false (mutation), destructiveHint=false (non-destructive), idempotentHint=true (safe to retry). The description adds that it 'stops and removes services,' which clarifies the specific mutation beyond annotations. However, it doesn't mention side effects like removing containers/networks or whether data volumes are preserved.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is brief but not optimally structured. The first sentence states the purpose clearly, but the Args/Returns sections are redundant with the schema and output schema. The text could be more front-loaded with critical usage information instead of repeating structured data.

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 complexity (mutation with 1 parameter but nested schema), annotations cover safety aspects well, and an output schema exists. However, the description lacks important context: it doesn't explain what 'removes' entails (containers, networks, volumes?), doesn't differentiate from sibling tools, and provides minimal parameter guidance despite 0% schema coverage.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It only states '包含项目目录' (contains project directory), which partially explains the 'params' object but doesn't cover the nested 'project_dir' and optional 'service' parameters. The description fails to explain what 'project_dir' means or how 'service' affects the operation.

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 tool's purpose: '使用 Docker Compose 停止并移除服务' (Use Docker Compose to stop and remove services). This is a specific verb+resource combination that distinguishes it from simple stop tools. However, it doesn't explicitly differentiate from sibling tools like 'orbstack_docker_stop' or 'orbstack_compose_up' beyond the Compose context.

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 to choose 'orbstack_compose_down' over 'orbstack_docker_stop' or 'orbstack_docker_rm', nor does it specify prerequisites like requiring a running Compose project. The only implied context is Docker Compose projects.

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