Skip to main content
Glama
gbatistuta0

AppFactory

by gbatistuta0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

ASC Create Bundle ID

asc_create_bundle_id
Destructive

Register a bundle ID in App Store Connect and check or apply its App ID capabilities, a required first step before signing a new app.

Instructions

Register a bundle id in App Store Connect and check or apply its App ID capabilities (live write, needs human approval).

Use when: first ASC step for a new app; capabilities (IN_APP_PURCHASE, Sign in with Apple, HEALTHKIT if enabled) must exist before signing. Not for: creating the app record (use asc_create_app). Returns: {bundle_id: , capabilities: <store_setup report>} or an approval_required refusal.

Input Schema

NameRequiredDescriptionDefault
nameYesHuman-readable name of the bundle id in the developer portal, e.g. 'My App'.
app_dirNoAbsolute path to the app project directory (contains app.spec.json), e.g. /Users/me/Apps/MyApp.
identifierYesBundle identifier to register, 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.
apply_capabilitiesNoIf true, also enable the spec's App ID capabilities (needs app_dir); false only checks them.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.1.5
    • addedInput schema / properties / app_dir / description
      Added value: +"Absolute path to the app project directory (contains app.spec.json), e.g. /Users/me/Apps/MyApp."
    • addedInput schema / properties / apply_capabilities / description
      Added value: +"If true, also enable the spec's App ID capabilities (needs app_dir); false only checks them."
    • 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 / identifier / description
      Added value: +"Bundle identifier to register, e.g. com.example.app."
    • addedInput schema / properties / name / description
      Added value: +"Human-readable name of the bundle id in the developer portal, e.g. 'My App'."
  2. First observedv0.1.1

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare destructive=true, openWorld=true, and idempotent=false, so the mutation/risk profile is covered. The description adds genuinely new behavioral context beyond that: the live-write-needs-human-approval requirement and the approval_required refusal path. It stops short of disclosing what a partial capability failure does or how retries interact with the created bundle id, so it falls just under full marks.

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 tightly structured blocks (purpose, Use when / Not for, Returns) with zero filler. The action and its routing constraint are front-loaded ahead of the return-shape detail.

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, approval-gated mutation this covers everything the agent needs: prerequisites (capabilities before signing), the sibling to use instead, the approval loop, and a return shape. An output schema exists, so the brief 'Returns' line is appropriately terse rather than duplicative.

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 coverage is 100%, so the baseline is 3 and the schema already documents all five parameters including approval_id and apply_capabilities. The description adds value by naming the concrete capabilities acted on (IN_APP_PURCHASE, Sign in with Apple, HEALTHKIT if enabled), which the boolean apply_capabilities does not convey.

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 ('Register a bundle id in App Store Connect') plus the secondary action (check or apply App ID capabilities). It explicitly distinguishes itself from the sibling asc_create_app, so an agent can route correctly 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 Guidelines5/5

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

Has an explicit 'Use when' (first ASC step for a new app; capabilities must exist before signing) and an explicit 'Not for' that names the alternative tool (asc_create_app). Both the positive and negative selection conditions are given.

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