Skip to main content
Glama
Zhuoli

macOS Tools MCP Server

by Zhuoli

diskutil_list

List all disks and partitions on macOS systems to view storage configuration and identify available drives.

Instructions

List all disks and partitions using diskutil list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • MCP tool handler function that delegates execution to the underlying tools.diskutil_list() implementation.
    def diskutil_list(_: Context | None = None) -> str:
        return tools.diskutil_list()
  • Registers the 'diskutil_list' tool with the FastMCP app, including name and description (implicit schema: no inputs, str output).
    @app.tool(
        name="diskutil_list",
        description="List all disks and partitions using `diskutil list`.",
    )
  • Core implementation that executes the 'diskutil list' shell command via _run_command helper.
    def diskutil_list() -> str:
        """Return the output of ``diskutil list`` for disk overview."""
        return _run_command(["diskutil", "list"])
Behavior2/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 behavioral disclosure. It states the action but doesn't describe what the output looks like (though an output schema exists), whether it requires admin privileges, if it's read-only or has side effects, or any rate limits. This is a significant gap for a tool with zero annotation coverage.

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, efficient sentence with zero waste. It's front-loaded with the core purpose and includes the specific command, making it appropriately sized and well-structured for its simplicity.

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 low complexity (0 parameters, output schema provided), the description is somewhat complete but has gaps. It states what the tool does but lacks behavioral context and usage guidelines. The output schema helps, but the description doesn't leverage this to explain return values or other aspects, making it minimally adequate.

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 with 100% schema description coverage, so the schema fully documents the lack of parameters. The description doesn't need to add parameter details, and it correctly implies no inputs are required by not mentioning any. Baseline for 0 parameters is 4, as it's complete in this regard.

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 ('List all disks and partitions') and the specific command used ('using `diskutil list`'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'system_profile' which might also provide system information, so it doesn't reach the highest score.

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 like 'system_profile' or other system information tools. There's no mention of context, prerequisites, or exclusions, leaving the agent without usage direction.

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/Zhuoli/mcp101'

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