Skip to main content
Glama

DevReply

by com.devreply
OverviewDiscussionsAdmin

Add a platform

add_platform

Adds iOS, Android or web to an app and creates that platform's permanent public key. Owners only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
app_idNoThe app's id (from list_apps). Optional when there is only one.
platformYesThe platform to add.
bundle_idNoBundle ID, package name or site domain.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
app_idYesThe app.
platformsYesIts platforms now.
public_keyYesA platform's public key (pk_), the one the app's code uses.
setup_guideYesThe setup guide's URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / platform / description
      Added value: +"The platform to add."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "app_id": {
+      "description": "The app.",
+      "format": "uuid",
+      "type": "string"
+    },
+    "platforms": {
+      "description": "Its platforms now.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "public_key": {
+      "description": "A platform's public key (pk_), the one the app's code uses.",
+      "properties": {
+        "key": {
+          "description": "The public key, pk_…",
+          "type": "string"
+        },
+        "platform": {
+          "description": "ios, android or web.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "platform",
+        "key"
+      ],
+      "type": "object"
+    },
+    "setup_guide": {
+      "description": "The setup guide's URL.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "app_id",
+    "platforms",
+    "public_key",
+    "setup_guide"
+  ],
+  "type": "object"
+}
  2. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-idempotent, non-destructive, and closed-world. The description adds two things beyond that: the resulting public key is 'permanent', and the caller must be an owner. It doesn't cover failure modes or whether an existing platform can be re-added, but it meaningfully extends the annotation picture.

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?

A single tight sentence front-loads the action and resource, then tacks on the side effect and the access constraint. Every clause earns its place with no redundancy.

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?

With an output schema present, return values need no explanation, and all three parameters are fully covered by the schema. The description supplies the key persistence and owner-only constraint, leaving only edge cases like duplicate platform handling unaddressed.

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 app_id, platform, and bundle_id are already documented, including the enum and the 'optional when there is only one' note on app_id. The description's 'iOS, Android or web' merely restates the enum and adds no format or constraint detail, so the baseline 3 applies.

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 states a specific verb and resource ('Adds iOS, Android or web to an app') and adds the key side effect, which cleanly separates it from siblings like create_app or update_app. An agent immediately knows this attaches a platform to an existing app rather than creating one.

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

Usage Guidelines3/5

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

The prerequisite 'Owners only' gives useful access guidance, but there is no explicit when-to-use vs alternatives (e.g. add_platform vs create_app vs set_ios_push_key) and no when-not-to-use conditions. Usage is only implied by the purpose.

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