Skip to main content
Glama
heresun

OrbStack MCP Server

by heresun

orbstack_k8s_start

Idempotent

Start the lightweight single-node Kubernetes cluster built into OrbStack to manage containerized applications on macOS.

Instructions

启动 OrbStack 内置的 Kubernetes 集群。

OrbStack 提供轻量级的单节点 K8s 集群。

Returns: str: 启动结果

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The implementation of the 'orbstack_k8s_start' tool. It is registered using the @mcp.tool decorator and calls the internal '_run_orb' function to execute the Kubernetes start command.
    @mcp.tool(
        name="orbstack_k8s_start",
        annotations={
            "title": "启动 Kubernetes",
            "readOnlyHint": False,
            "destructiveHint": False,
            "idempotentHint": True,
            "openWorldHint": False,
        },
    )
    async def orbstack_k8s_start() -> str:
        """启动 OrbStack 内置的 Kubernetes 集群。
    
        OrbStack 提供轻量级的单节点 K8s 集群。
    
        Returns:
            str: 启动结果
        """
        code, stdout, stderr = await _run_orb(["k8s", "start"], timeout=120)
Behavior4/5

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

Annotations provide key hints (idempotentHint=true, destructiveHint=false, readOnlyHint=false), but the description adds valuable context: it specifies the cluster is lightweight and single-node, which helps set expectations. No contradiction with annotations exists, and it complements them by describing the cluster type.

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 front-loaded with the core action, followed by additional context about the cluster and return value. Each sentence adds value: the first states the purpose, the second provides cluster details, and the third specifies the return type. No wasted words.

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?

Given 0 parameters, rich annotations (idempotent, non-destructive), and an output schema (implied by 'Returns: str'), the description is complete. It covers purpose, cluster characteristics, and return type, leaving no gaps for an AI agent to understand and invoke the tool correctly.

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?

There are 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description appropriately focuses on the tool's purpose and behavior without redundant parameter details, earning a baseline score of 4 for zero-parameter tools.

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 specific action ('启动' meaning 'start') and resource ('OrbStack 内置的 Kubernetes 集群' meaning 'OrbStack's built-in Kubernetes cluster'), distinguishing it from sibling tools like orbstack_k8s_stop and orbstack_k8s_status. It also mentions the cluster is lightweight and single-node, adding useful context.

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?

The description implies usage when needing to start the Kubernetes cluster, with clear context from sibling tools (e.g., use orbstack_k8s_stop to stop it, orbstack_k8s_status to check status). However, it lacks explicit when-not-to-use guidance or prerequisites, such as whether OrbStack must be running first.

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