Skip to main content
Glama
g0t4

macOS Defaults MCP Server

by g0t4

find

Search macOS system preferences and application settings for entries containing specific words to locate configuration options.

Instructions

Find entries container given word

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
wordNoWord to search for

Implementation Reference

  • The handler function for the 'find' tool. It extracts the 'word' from arguments and runs the macOS 'defaults find <word>' command via subprocess, returning the output as TextContent.
    def find(arguments: dict | None) -> list[types.TextContent]: # ask for help to find a setting, that alone is possibly very useful
        if arguments is None:
            raise ValueError("Arguments are required")
        word = arguments["word"]
        result = subprocess.run(["defaults", "find", word], capture_output=True)
        return [types.TextContent(type="text", text=f"Found: {result.stdout.decode('utf-8')}")]
  • JSON Schema definition for the 'find' tool input, specifying a required 'word' string argument.
    types.Tool(
        name="find",
        description="Find entries container given word",
        inputSchema= {
            "type": "object",
            "properties": {
                "word": {
                    "type": "string",
                    "description": "Word to search for",
                },
            },
        },
    ),
  • Registration dispatch in the @server.call_tool() handler that routes calls to the 'find' function.
    elif name == "find":
        return find(arguments)
Behavior2/5

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

With no annotations, the description carries full burden but provides minimal behavioral insight. It mentions searching but doesn't disclose traits like read-only vs. destructive, permissions needed, rate limits, or what 'find' entails (e.g., exact match, partial). This leaves significant gaps for a tool with unknown behavior.

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 a single, compact sentence with no wasted words, making it efficient. However, it lacks front-loading of critical details and could be more structured to clarify purpose upfront.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations, no output schema, and a vague purpose, the description is incomplete. It doesn't explain what 'entries container' refers to, the return format, or behavioral context, making it inadequate for effective tool selection and invocation.

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

Parameters3/5

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

Schema description coverage is 100%, with the parameter 'word' documented as 'Word to search for'. The description adds no meaning beyond this, merely restating 'given word'. Baseline 3 is appropriate as the schema handles parameter documentation adequately.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the action ('find') and target ('entries container'), but it's vague about what 'entries container' means and doesn't distinguish from sibling tools like 'list-domains'. The phrase 'given word' is redundant with the parameter name, reducing specificity.

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?

No guidance is provided on when to use this tool versus alternatives like 'list-domains' or 'defaults-read'. The description implies usage for searching by word, but lacks context about prerequisites, exclusions, or comparison to siblings.

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/g0t4/mcp-server-macos-defaults'

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