Skip to main content
Glama
Sign In
simctl-mcp-server

simctl-mcp-server

by nzrsky
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

simctl_push_notification

Send a push notification to an iOS simulator device using a JSON payload and optional bundle identifier for testing app responses.

Instructions

Send a push notification to a simulator device.

Args: device: Device UDID, name, or 'booted' for current device payload: Push notification payload as JSON object bundle_id: Target app bundle identifier (optional if specified in payload)

Returns: Success message

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": {
      "device": "<device>",
      "payload": "<payload>"
    },
    "name": "simctl_push_notification"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceYes
payloadYes
bundle_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It correctly identifies the tool as a write operation (sending a notification) and notes that bundle_id is optional. However, it does not disclose potential side effects, whether the device must be booted, or any security implications.

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 very concise: a single-sentence purpose, followed by a clear argument list and return type. Every sentence adds value; no redundant or filler content.

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 three parameters and an output schema, the description covers the basics. However, it omits important details like required payload format (Apple Push Notification service) and the fact that the simulator must be booted. The output schema may provide some return info, but the description only says 'Success message'.

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 description adds meaning beyond the schema: it specifies that device accepts 'UDID, name, or 'booted'', payload is a 'JSON object', and bundle_id is 'target app bundle identifier (optional)'. This clarifies intent beyond the schema's titles and types.

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

Purpose5/5

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

The description clearly states the action: 'Send a push notification to a simulator device.' It uses a specific verb ('Send') and resource ('push notification to simulator device'), which distinguishes it from sibling tools that handle device management, app installation, or launching.

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, nor any prerequisites or conditions such as requiring a booted simulator or specific permissions. The description only lists parameters without context on appropriate use.

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