Skip to main content
Glama
Sign In
Apple Ecosystem MCP

Apple Ecosystem MCP

by abhinavag-svg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Add Apple Alias

apple_preferences_add_alias

Creates an alias for a scope target in Apple System Preferences, enabling direct access to specific settings via a custom name.

Instructions

Add an alias for a scope target.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "scope": "<scope>",
      "alias": "<alias>",
      "id": "<id>",
      "name": "<name>",
      "kind": "<kind>"
    },
    "name": "apple_preferences_add_alias"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
kindYes
nameYes
pathNo
aliasYes
scopeYes
account_nameNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.2

TDQS

C2.2/5.0
Behavior2/5

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

Annotations provide no behavioral hints (readOnly, destructive), so the description must inform. It only says 'Add' implying creation, but no details on side effects, permissions, or error cases.

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

Conciseness3/5

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

One sentence, concise but too brief; lacks structure to convey essential information for agent usage.

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?

With 7 parameters and no parameter explanations, and an output schema not described, the description is insufficient for proper invocation despite the output schema existing.

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

Parameters1/5

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

Schema has 0% description coverage, and the description adds no meaning to any of the 7 parameters. It does not explain the role of 'scope', 'alias', 'id', etc.

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 'Add an alias for a scope target,' which identifies the action and resource but does not clarify what a scope target is or differentiate from sibling tools.

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 on when to use this tool instead of alternatives like apple_preferences_remove_alias or others. Lacks context for invocation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools