Skip to main content
Glama
Sign In
Xcode MCP Server

Xcode MCP Server

by ebowwa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

xcode_add_plist_entry

Add new entries to plist files in Xcode projects by specifying key, type, and value parameters for configuration management.

Instructions

Add a new entry to a plist file

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": {
      "plist_path": "<plist_path>",
      "key": "<key>",
      "type": "<type>",
      "value": "<value>"
    },
    "name": "xcode_add_plist_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
plist_pathYesPath to the plist file
keyYesPlist key to add
typeYesValue type (string, bool, integer, array, dict)
valueYesValue to add

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/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 the tool adds an entry, implying a write operation, but doesn't mention permissions needed, whether it overwrites existing keys, error handling, or file system impacts. This leaves significant behavioral gaps for a mutation tool.

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, making it easy to scan and understand quickly without unnecessary elaboration.

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?

For a mutation tool with no annotations and no output schema, the description is inadequate. It doesn't explain what happens on success/failure, return values, or edge cases like duplicate keys. Given the complexity of modifying plist files, more context is needed for safe and effective use.

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%, so the schema fully documents all four parameters. The description adds no additional parameter semantics beyond what's in the schema, such as format examples or constraints. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('Add a new entry') and target resource ('to a plist file'), providing specific verb+resource. However, it doesn't distinguish this tool from its sibling 'xcode_modify_plist', which appears to handle similar plist operations, leaving some ambiguity about when to use each.

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 'xcode_modify_plist' or other plist-related operations. The description lacks context about prerequisites, typical use cases, or any exclusions, offering minimal usage direction.

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