Skip to main content
Glama

DevReply

by com.devreply
OverviewDiscussionsAdmin

Set the Android push key

set_android_push_key
Idempotent

Uploads the app's Firebase service account (the JSON file's contents) so Android users get pushes for replies through FCM. Stored encrypted, never shown again. Owners only. The person creates it once: Firebase console → Project settings → Service accounts → Generate new private key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
app_idNoThe app's id (from list_apps). Optional when there is only one.
service_accountYesThe service-account JSON, as text.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pushYesPush setup (never the keys themselves).
app_idYesThe app.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
+}
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Adds behavior beyond the annotations: the credential is 'Stored encrypted, never shown again' (a write-only secret an agent must not expect to read back) and the call requires owner-level auth. That is real context on top of readOnlyHint=false and idempotentHint=true, though re-upload/overwrite semantics are left to the idempotency annotation.

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

Conciseness4/5

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

Three tight sentences, front-loaded with the action and effect, then the security/store constraint, then the auth and acquisition steps. The console navigation path is slightly list-like but it is genuinely actionable information rather than filler.

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 no explanation, and the schema fully documents both parameters including the optional single-app case for app_id. Auth requirements, secrecy of the stored key, and where the credential originates are all covered, leaving nothing an agent needs before calling it.

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?

Schema coverage is already 100%, so baseline is 3. The description still adds meaning by explaining what the service_account string actually is and how to obtain it (Firebase console → Project settings → Service accounts → Generate new private key), which the schema's 'as text' wording does not convey.

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 Firebase service account), plus the outcome (Android users get pushes for replies via FCM). It is clearly distinguishable from the sibling set_ios_push_key and from set_app_icon/update_app.

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 explicit prerequisites and timing: 'Owners only' and 'The person creates it once,' with a step-by-step pointer to where the key comes from in the Firebase console. It does not name set_ios_push_key as the alternative for iOS devices, which is the one routing cue an agent might still want.

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

All DevReply toolsInspect
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