Skip to main content
Glama
heresun

OrbStack MCP Server

by heresun

orbstack_docker_images

Read-onlyIdempotent

List all local Docker images in a formatted table to manage container resources on macOS through OrbStack.

Instructions

列出本地所有 Docker 镜像。

Returns: str: 镜像列表(格式化表格)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function `orbstack_docker_images` that executes `docker images` and returns the formatted output.
    async def orbstack_docker_images() -> str:
        """列出本地所有 Docker 镜像。
    
        Returns:
            str: 镜像列表(格式化表格)
        """
        args = ["images", "--format", "table {{.Repository}}\t{{.Tag}}\t{{.ID}}\t{{.Size}}\t{{.CreatedSince}}"]
        code, stdout, stderr = await _run_docker(args)
        if code != 0:
            return _format_error(stderr)
        if not stdout:
  • Registration of the `orbstack_docker_images` tool using the @mcp.tool decorator.
    @mcp.tool(
        name="orbstack_docker_images",
        annotations={
            "title": "列出 Docker 镜像",
            "readOnlyHint": True,
            "destructiveHint": False,
            "idempotentHint": True,
            "openWorldHint": False,
        },
    )
Behavior3/5

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

Annotations already indicate read-only, non-destructive, and idempotent behavior. The description adds minimal context by specifying the output format ('格式化表格' - formatted table), which is useful but doesn't detail aspects like sorting, filtering, or error handling. No contradiction with annotations exists.

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

Conciseness4/5

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

The description is brief and front-loaded, stating the core purpose in the first sentence. The second sentence about the return value adds necessary clarity without redundancy. However, it could be slightly more structured by explicitly separating purpose and output.

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 the tool's simplicity (0 parameters, read-only), annotations cover safety aspects, and an output schema exists (implied by 'Has output schema: true'), the description is reasonably complete. It specifies the output format, which complements the structured data, though more behavioral details like performance or limitations could enhance it.

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?

With 0 parameters and 100% schema description coverage, the baseline is high. The description doesn't need to explain parameters, and it appropriately focuses on the action and output. No additional parameter semantics are required or provided.

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 verb '列出' (list) and resource '本地所有 Docker 镜像' (all local Docker images), making the purpose evident. However, it doesn't explicitly differentiate from sibling tools like 'orbstack_docker_ps' (which lists containers) or 'orbstack_machine_list' (which lists machines), missing full sibling distinction.

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 scenarios like checking for available images before running containers or comparing with 'orbstack_docker_pull' for fetching new images, leaving usage context implied at best.

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