DevReply

Create an app

create_app

A new app in the organization, starting with one platform (add the others with add_platform). Returns its public key and setup guide link. Owners only.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	The app's name, as users see it in the chat.
`platform`	Yes	The first platform.
`bundle_id`	No	Bundle ID, package name or site domain. Optional.

Output Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Its name.
`next`	Yes	What to do next.
`app_id`	Yes	The new app's id.
`platforms`	Yes	Its platforms.
`public_key`	Yes	A platform's public key (pk_), the one the app's code uses.
`setup_guide`	Yes	The setup guide's URL.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 5, 2026

addedInput schema / properties / bundle_id / description

Added value: +"Bundle ID, package name or site domain. Optional."

addedInput schema / properties / name / description

Added value: +"The app's name, as users see it in the chat."

addedInput schema / properties / platform / description
```
Added value: +"The first platform."
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "app_id": {
+      "description": "The new app's id.",
+      "format": "uuid",
+      "type": "string"
+    },
+    "name": {
+      "description": "Its name.",
+      "type": "string"
+    },
+    "next": {
+      "description": "What to do next.",
+      "type": "string"
+    },
+    "platforms": {
+      "description": "Its platforms.",
+      "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",
+    "name",
+    "platforms",
+    "public_key",
+    "setup_guide",
+    "next"
+  ],
+  "type": "object"
+}

AddedOct 5, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, closed-world mutation, so the safety bar is partly covered. The description adds real value beyond that: the authorization requirement ('Owners only'), the single-platform starting state, and what the call yields (public key, setup guide link).

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 short sentences, no filler, with the core action and the platform-routing constraint front-loaded. The opening noun phrase is slightly telegraphic but the title supplies the verb, so it costs nothing.

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?

An output schema exists, so return values need not be enumerated, yet the description still flags the public key and setup guide link. Combined with the Owners-only caveat and the add_platform pointer, an agent has everything needed to invoke it correctly; only edge cases like name collisions or errors are 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% and each of the three parameters is documented in-schema, so the baseline is 3. The description reinforces the platform parameter's meaning ('starting with one platform') but adds nothing about name or bundle_id beyond the 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 gives a specific verb+resource (create a new app in the organization) and immediately scopes it: the app starts with a single platform. It explicitly distinguishes itself from the sibling add_platform, which handles subsequent platforms, so an agent can route between them without opening either schema.

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?

It names the alternative for the adjacent case ('add the others with add_platform') and states the 'Owners only' precondition, which tells the agent when the call is even permitted. It does not spell out when to prefer create_app over update_app or list_apps, but creation is unambiguous enough that this is a minor gap.

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?