Skip to main content
Glama
gbatistuta0

AppFactory

by gbatistuta0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Signing Create Profile

signing_create_profile
Destructive

Create an iOS App Store provisioning profile and write it to standard locations after signing_setup_distribution; requires human approval before live write.

Instructions

Create an IOS_APP_STORE provisioning profile and write it to the standard locations (live write, needs human approval).

Use when: after signing_setup_distribution; testflight_ship does this for you. Returns: {ok, profile_id, name, path}.

Input Schema

NameRequiredDescriptionDefault
nameNoProvisioning profile name (default 'AppFactory AppStore').AppFactory AppStore
cert_idYesApp Store Connect certificate id from signing_setup_distribution.
bundle_idYesApp bundle identifier in reverse-DNS form, e.g. com.example.app.
approval_idNoApproval id from a previous approval_required refusal; omit on the first call. The human approves out-of-band with `appfactory approve <id>`, then call again with the same arguments and this id.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.5
    • addedInput schema / properties / approval_id / description
      Added value: +"Approval id from a previous approval_required refusal; omit on the first call. The human approves out-of-band with `appfactory approve <id>`, then call again with the same arguments and this id."
    • addedInput schema / properties / bundle_id / description
      Added value: +"App bundle identifier in reverse-DNS form, e.g. com.example.app."
    • addedInput schema / properties / cert_id / description
      Added value: +"App Store Connect certificate id from signing_setup_distribution."
    • addedInput schema / properties / name / description
      Added value: +"Provisioning profile name (default 'AppFactory AppStore')."
  2. First observedv0.1.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already flag destructive=true, idempotent=false, openWorld=true, and the description still adds the crucial operational facts: this is a live write to disk and it requires human approval. It doesn't detail failure modes or what happens to an existing profile of the same name, so it stops short of a 5.

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 front-loaded chunks (what, when, returns) with zero filler; the destructive 'live write, needs human approval' caveat is surfaced before the usage guidance.

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 destructive, non-idempotent write with an output schema present, the description covers purpose, prerequisites, the approval gate, and the return shape. Nothing an agent needs to call it correctly is missing.

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 the approval_id parameter already documents the out-of-band approval loop, so the description has little left to add beyond naming the return fields. Baseline 3 applies when the schema does the heavy lifting.

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 and resource ('Create an IOS_APP_STORE provisioning profile') and even the side effect ('write it to the standard locations'). It names the sibling tools it relates to (signing_setup_distribution, testflight_ship), so an agent can place it without opening the 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?

The 'Use when: after signing_setup_distribution; testflight_ship does this for you' line gives both the triggering prerequisite and an explicit alternative path, which is exactly the routing guidance an agent needs.

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

Deploy Server

Other Tools