Skip to main content
Glama
Zhuoli

macOS Tools MCP Server

by Zhuoli
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

battery_status

Check macOS battery charge level and status using system utilities. Retrieve current battery information for monitoring power usage.

Instructions

Show current battery information reported by pmset -g batt.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • macos_tools_mcp/tools.py:71-73 (handler)
    Core handler function implementing the battery_status tool by executing `pmset -g batt` command.
    def battery_status() -> str:
    """Return the battery summary from ``pmset -g batt``."""
    return _run_command(["pmset", "-g", "batt"])
  • macos_tools_mcp/server.py:27-32 (registration)
    Registers the battery_status tool with FastMCP server, providing a thin wrapper that delegates to tools.battery_status().
    @app.tool(
    name="battery_status",
    description="Show current battery information reported by `pmset -g batt`.",
)
def battery_status(_: Context | None = None) -> str:
    return tools.battery_status()

Tool Definition Quality

B3.2/5.0
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 what command will be executed ('pmset -g batt') but doesn't describe what happens when invoked - whether it requires permissions, how long it takes, what format the output will be in, or any error conditions. For a tool with zero annotation coverage, this is a significant gap in behavioral transparency.

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 - a single sentence that directly states what the tool does and how it works. Every word earns its place: 'Show current battery information' defines the purpose, and 'reported by `pmset -g batt`' provides implementation context. There's zero waste or redundancy.

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 that the tool has no parameters, 100% schema coverage, and an output schema exists, the description is reasonably complete for its complexity level. However, for a system tool that executes a shell command, the description could benefit from mentioning typical output format or common use cases. The existence of an output schema means the description doesn't need to explain return values, but additional context about the tool's behavior would be helpful.

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 already fully documents the parameter situation. The description appropriately doesn't discuss parameters since none exist. This earns a baseline 4 for parameter semantics as the description doesn't need to compensate for any parameter documentation gaps.

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: 'Show current battery information' with the specific source 'reported by `pmset -g batt`'. This provides a specific verb ('show') and resource ('battery information') with implementation details. However, it doesn't explicitly differentiate from sibling tools like 'system_profile' which might also provide system information.

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 versus using 'system_profile' or other system monitoring tools, nor does it provide any context about prerequisites, timing considerations, or limitations. The agent must infer usage from the tool name and description alone.

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