Skip to main content
Glama
gbatistuta0

AppFactory

by gbatistuta0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

ASC Ensure Subscription Prices

asc_ensure_subscription_prices
DestructiveIdempotent

Set prices on app subscriptions missing one to clear MISSING_METADATA; already priced subscriptions are skipped. Live write needs human approval.

Instructions

Set a price on every subscription of the app that has none, clearing MISSING_METADATA (live write, needs human approval).

Use when: subscriptions are stuck in MISSING_METADATA for price. Idempotent: priced subscriptions are skipped. Returns: {ok, priced: [...], skipped: [...]} or an approval_required refusal.

Input Schema

NameRequiredDescriptionDefault
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.
default_usdNoUSD price string applied to subscriptions not listed in usd_price_by_product.
usd_price_by_productNoMap of subscription productId to USD price string, e.g. {'com.example.app.yearly': '49.99'}.

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 / default_usd / description
      Added value: +"USD price string applied to subscriptions not listed in usd_price_by_product."
    • addedInput schema / properties / usd_price_by_product / description
      Added value: +"Map of subscription productId to USD price string, e.g. {'com.example.app.yearly': '49.99'}."
  2. First observedv0.1.1

TDQS

A4.3/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: a live write requiring human approval, an out-of-band approval flow via approval_required refusal, and skip semantics ('Idempotent: priced subscriptions are skipped'). Annotations already declare destructiveHint and idempotentHint, but the description supplies the approval workflow and exact return shape that an agent needs.

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 tight sentences, front-loaded with the action, followed by the trigger condition and return shape. Every sentence carries unique information and there is no redundancy.

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?

Covers purpose, when-to-use, idempotency, approval requirement, and return/refusal outcomes. With an output schema present and annotations covering safety, the description is complete enough for an agent to invoke 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 four parameters including the approval_id workflow are already documented in the schema. The description adds no parameter-level syntax or format detail beyond what the schema provides, making the baseline 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Set a price on every subscription of the app that has none'. The MISSING_METADATA condition makes the scope distinctive, but no sibling tool is named as an alternative, so it stops short of full sibling differentiation.

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

Usage Guidelines4/5

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

Gives an explicit trigger: 'Use when: subscriptions are stuck in MISSING_METADATA for price.' This is clear context for invocation, though it does not state when not to use the tool or name an alternative for other pricing scenarios.

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