DevReply

Set the iOS push key

set_ios_push_key

Idempotent

Uploads the app's APNs key (.p8 contents, Key ID, Team ID, bundle ID) so users get pushes for replies. Stored encrypted, never shown again. Owners only. Apple has no API to create the key: the person downloads it once.

Input Schema

TableJSON Schema

Name	Required	Description
`p8`	Yes	The .p8 file's contents, from -----BEGIN PRIVATE KEY----- to the end.
`app_id`	No	The app's id (from list_apps). Optional when there is only one.
`key_id`	Yes	The key's 10-character Key ID, e.g. ABC123DEFG (in the .p8's file name).
`team_id`	Yes	The 10-character Apple Team ID (Apple Developer, Membership).
`bundle_id`	Yes	The app's bundle ID, e.g. com.example.app.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`push`	Yes	Push setup (never the keys themselves).
`app_id`	Yes	The app.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 5, 2026

addedInput schema / properties / bundle_id / description

Added value: +"The app's bundle ID, e.g. com.example.app."

addedInput schema / properties / key_id / description

Added value: +"The key's 10-character Key ID, e.g. ABC123DEFG (in the .p8's file name)."

addedInput schema / properties / p8 / description

Added value: +"The .p8 file's contents, from -----BEGIN PRIVATE KEY----- to the end."

addedInput schema / properties / team_id / description

Added value: +"The 10-character Apple Team ID (Apple Developer, Membership)."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "app_id": {
+      "description": "The app.",
+      "format": "uuid",
+      "type": "string"
+    },
+    "push": {
+      "description": "Push setup (never the keys themselves).",
+      "properties": {
+        "android": {
+          "description": "The Firebase service account, or null when none is uploaded.",
+          "properties": {
+            "client_email": {
+              "description": "The service account's email.",
+              "type": "string"
+            },
+            "last_error": {
+              "description": "The last error from the push service, if any.",
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "last_sent_at": {
+              "description": "The last push sent with this service account.",
+              "format": "date-time",
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "project_id": {
+              "description": "The Firebase project id.",
+              "type": "string"
+            },
+            "updated_at": {
+              "description": "When it was uploaded.",
+              "format": "date-time",
+              "type": "string"
+            }
+          },
+          "type": [
+            "object",
+            "null"
+          ]
+        },
+        "android_devices": {
+          "description": "Android installs that can receive pushes.",
+          "type": "integer"
+        },
+        "available": {
+          "description": "Push is enabled on this DevReply server.",
+          "type": "boolean"
+        },
+        "ios": {
+          "description": "The APNs key, or null when none is uploaded.",
+          "properties": {
+            "bundle_id": {
+              "description": "The bundle ID pushes go to.",
+              "type": "string"
+            },
+            "key_id": {
+              "description": "The APNs Key ID.",
+              "type": "string"
+            },
+            "last_error": {
+              "description": "The last error from the push service, if any.",
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "last_sent_at": {
+              "description": "The last push sent with this key.",
+              "format": "date-time",
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "team_id": {
+              "description": "The Apple Team ID.",
+              "type": "string"
+            },
+            "updated_at": {
+              "description": "When it was uploaded.",
+              "format": "date-time",
+              "type": "string"
+            }
+          },
+          "type": [
+            "object",
+            "null"
+          ]
+        },
+        "ios_devices": {
+          "description": "iOS installs that can receive pushes.",
+          "type": "integer"
+        },
+        "taps_seen_at": {
+          "description": "When the app last opened a DevReply notification (taps reach the chat).",
+          "format": "date-time",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "available",
+        "ios_devices",
+        "android_devices",
+        "taps_seen_at",
+        "ios",
+        "android"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "app_id",
+    "push"
+  ],
+  "type": "object"
+}

AddedOct 5, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly=false, idempotent=true, destructive=false). The description adds meaningful behavioral context beyond them: the key is stored encrypted, it is never shown again after upload, the operation requires owner privileges, and the credential must be sourced out-of-band from Apple. The only missing piece is whether re-uploading replaces an existing key, though idempotentHint implies 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?

Three tight sentences, each earning its place: what is uploaded, how it is stored and its one-time visibility, who may call it, and why the caller must obtain the key externally. No redundancy with the title or schema.

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

Completeness5/5

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

An output schema exists, so return values need not be explained. For a credential-upload mutation the description covers authorization (owners only), security handling (encrypted, never shown again), and the external prerequisite (Apple has no creation API) — everything an agent needs to call it correctly.

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 every parameter including the optional app_id is already documented in the schema. The description restates the payload components but adds no format, validation, or edge-case detail beyond what the schema provides. Baseline 3 applies 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.

Purpose5/5

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

States a specific verb (uploads) and resource (the app's APNs key), enumerating exactly what the payload contains (.p8 contents, Key ID, Team ID, bundle ID). It is trivially distinguishable from the sibling set_android_push_key, and the purpose (delivering push notifications for replies) is stated explicitly.

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?

Gives a clear precondition — 'Owners only' — and contextualizes the workflow by noting Apple provides no API to create the key so the user must download it first. It does not explicitly contrast with set_android_push_key, but the iOS scope makes the alternative obvious from the name.

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

All DevReply tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?