Skip to main content
Glama
Sign In

HotCodePush

by com.hotcodepush
OverviewDiscussionsAdmin

Create an app

create_app

Create an app in an organization with its default channel production. Use this once per mobile app, naming the framework it is built with; the returned id is the appId the project's hotcodepush.json and every other tool take. Counts against the organization's appCountLimit; the name is unique per organization. Returns the created app with id, name, framework and defaultChannelId. Do not use this to create a channel (use create_channel) or an organization (use create_organization).

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": {
      "organizationId": "<organizationId>",
      "framework": "<framework>",
      "name": "<name>"
    },
    "name": "create_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe name of the app, e.g. "Acme Mobile".
frameworkYesThe framework the app is built with: "react_native", "expo", "capacitor" or "cordova".
organizationIdYesThe id of the organization, e.g. "a1b2c3d4-0000-4000-8000-000000000000". Use `list_organizations` to look it up.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only say it is a non-read-only, non-destructive, open-world write; the description adds the material behavior: a `production` default channel is created alongside, the call consumes the organization's `appCountLimit`, and the name must be unique per organization (an error condition). It also states the return shape, which is needed since no output schema exists.

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 sentences, front-loaded: purpose and side effect first, then the workflow consequence (returned `id` is the `appId` used everywhere else), then the exclusions. No sentence repeats a structured field verbatim, and every clause carries information an agent would otherwise have to guess.

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?

For a 3-required-param mutation with no output schema, the description covers the side effect, quota consumption, uniqueness constraint, return fields, and downstream use of the returned id. Nothing needed to call it correctly or to interpret the result is missing.

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 description coverage is 100%, so the baseline is 3; the description earns above that by adding constraints not in the schema — the name's uniqueness per organization and the meaning of `framework` as the build framework of the app. It does not add per-parameter format detail beyond the schema, which is already thorough.

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?

Specific verb+resource ("Create an app in an organization") with the side effect surfaced immediately ("with its default channel `production`"). It explicitly names the siblings it is not — `create_channel` and `create_organization` — so an agent can disambiguate within a large create_* family without opening any schema.

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

Usage Guidelines5/5

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

Gives an explicit usage cadence ("Use this once per mobile app") plus the prerequisite framing (naming the framework it is built with), and closes with hard exclusions pointing to the correct alternatives. Both when-to-use and when-not-to-use are stated, not implied.

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

All HotCodePush toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources