Skip to main content
Glama
gbatistuta0

AppFactory

by gbatistuta0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

ASC Finalize Subscription

asc_finalize_subscription
DestructiveIdempotent

Finalize one App Store Connect subscription by applying localization, availability, price, and intro offer in sequence; returns step results or an approval request before live writes.

Instructions

Finalize one subscription in order: localization, availability (all but CHN), price, intro offer (live write, needs human approval).

Use when: fixing a single product by hand. Prefer store_setup, which does every product idempotently. Pass the spec product's intro (e.g. {"type": "free", "duration": "P3D"}); offer products get no intro. Returns: {ok, steps...} per step, or an approval_required refusal.

Input Schema

NameRequiredDescriptionDefault
nameYesSubscription display name shown to users (en-US).
introNoIntro offer from the spec product, e.g. {"type": "free", "duration": "P3D"}; omit for offer products (no intro).
periodNoIgnored; kept for backward compatibility.
sub_idYesApp Store Connect subscription id.
usd_priceYesUSD base price as a decimal string, e.g. '49.99'.
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.
descriptionYesSubscription description shown to users (en-US).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 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 / description / description
      Added value: +"Subscription description shown to users (en-US)."
    • addedInput schema / properties / intro / description
      Added value: +"Intro offer from the spec product, e.g. {\"type\": \"free\", \"duration\": \"P3D\"}; omit for offer products (no intro)."
    • addedInput schema / properties / name / description
      Added value: +"Subscription display name shown to users (en-US)."
    • addedInput schema / properties / period / description
      Added value: +"Ignored; kept for backward compatibility."
    • addedInput schema / properties / sub_id / description
      Added value: +"App Store Connect subscription id."
    • addedInput schema / properties / usd_price / description
      Added value: +"USD base price as a decimal string, e.g. '49.99'."
  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 declare destructive/idempotent/openWorld hints, but the description adds material context beyond them: 'live write, needs human approval', the approval_required refusal, availability excluding CHN, and the per-step return shape. It stops short of detailing exactly what the live write mutates, but the approval workflow is a meaningful disclosure.

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?

Front-loads the operation and its ordered steps, then 'Use when' guidance, then the return contract. Every sentence carries distinct information with no padding.

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?

Given an output schema exists, return values need not be explained, yet the description still gives the shape and the approval refusal path. Combined with rich annotations and full schema coverage, an agent has everything needed to call it correctly.

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%, so all 7 parameters including approval_id and intro are already documented in the schema. The description only restates the intro example ('P3D') and offer-product rule, adding marginal value over 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?

States a specific verb+resource ('Finalize one subscription') and even enumerates the ordered sub-steps (localization, availability, price, intro offer). It distinguishes itself from sibling store_setup by scoping to a single product.

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?

Explicit 'Use when: fixing a single product by hand' and names the preferred alternative store_setup with the reason (does every product idempotently). Clear when-to-use and routing to the better tool is fully specified.

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