Skip to main content
Glama
Sign In
mobile-simulator-emulator-mcp

mobile-simulator-emulator-mcp

by gitsoufiane
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Send iOS Simulator Push

mobile_send_push

Send APNs push notification JSON payloads to installed iOS Simulator apps. Specify device and app ID for targeting.

Instructions

Send an APNs JSON payload to an installed iOS Simulator app. Android FCM has no equivalent adb command.

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>",
      "appId": "<appId>",
      "payload": "<payload>"
    },
    "name": "mobile_send_push"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdYes
deviceYesStable device ID returned by mobile_list_devices
payloadYes

Output Schema

NameRequiredDescriptionDefault
appIdYes
bytesYes
deviceYes
pushedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations indicate mutating action (readOnlyHint false) and not destructive (destructiveHint false). Description adds that it sends a push payload but does not detail idempotency, side effects (e.g., replacing vs. adding to notification queue), or authentication/payload constraints. With low annotation detail, description carries burden but only partly addresses it.

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?

Two sentences with no redundant information. First sentence states action and target, second provides a useful cross-platform comparison. Every word earns its place.

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

Completeness4/5

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

Tool has output schema (assumed present) and description covers purpose and platform. It references mobile_list_devices for device ID, aiding chaining. However, lacks details like APNs certificate requirement or payload format specifics. Minor gaps but sufficient for a focused tool.

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

Parameters2/5

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

Schema description coverage is only 33% (device parameter has a description). appId and payload have no description in schema, and the tool description does not elaborate on them beyond naming. Payload is described as 'APNs JSON' but no structure details. The description adds minimal value over schema.

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 it sends an APNs JSON payload to an installed iOS Simulator app. It also mentions the Android FCM has no equivalent, distinguishing it from any cross-platform tool. The verb 'send' and resource 'payload to app' are specific.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states that Android FCM has no equivalent adb command, implying this tool is iOS-only. It does not provide explicit when-not-to-use or alternative tool names, but the sibling list includes no other push tools, so the context is clear. Lacks explicit preconditions like app must be installed.

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