Skip to main content
Glama

appcrane_create_managed_app

Create a new app using AppCrane's GitHub service-account without requiring a personal access token. Automatically repairs the repo if a prior attempt failed.

Instructions

Create a new app using AppCrane's GitHub service-account — the platform creates a repo on the configured org/user, owns it, and the agent works against it through github_* tools without the end user ever needing their own PAT. Use this when the user does not have a GitHub account or does not want to deal with GitHub at all. Requires the platform admin to have configured the service-account in Settings → GitHub. Returns the same shape as appcrane_create_app, plus the auto-created repo metadata. IDEMPOTENT RECOVERY: if the slug already exists as a managed app but its AMC_ repo was never created (a half-created app from an earlier failure — push then returns REPO_NOT_FOUND), calling this again re-provisions the missing repo and returns { repaired: true } instead of erroring. So if a create attempt half-failed, just call it again with the same slug. Owner-or-admin to repair an existing one.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesDisplay name (human-readable)
slugYesURL slug, lowercase-alphanumeric-with-dashes. Becomes the repo name.
branchNoDefault branch for the new repo. Defaults to "main".
domainNoOptional custom domain.
max_ram_mbNoPer-container memory cap. Default: 512.
descriptionNoOptional. Used as both app description and repo description.
max_cpu_percentNoPer-container CPU cap. Default: 50.
Behavior5/5

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

No annotations provided, but description comprehensively discloses behavior: creates repo on org/user, platform ownership, agent workflow, return shape, and idempotent recovery with { repaired: true }. No contradictions.

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?

Well-structured with main purpose, usage, return info, and recovery details. Every sentence adds value, though could be slightly more concise.

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?

Given 7 parameters with full schema, no output schema, and no annotations, the description covers key behaviors, usage, and recovery. Missing explicit return format but reasonably complete.

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 covers all 7 parameters with descriptions. The description adds no additional parameter-level information beyond what the schema already provides. Baseline 3 is appropriate.

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?

Clearly states it creates a new app using a GitHub service-account, distinguishes from appcrane_create_app by specifying the service-account approach and additional repo metadata, and includes idempotent recovery details.

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?

Explicitly states when to use: when user does not have a GitHub account or wants to avoid GitHub. Also provides prerequisite (admin-configured service-account) and recovery guidelines for half-failed creates.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/gitayg/appcrane-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server