Skip to main content
Glama
gbatistuta0

AppFactory

by gbatistuta0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Backend Deploy

backend_deploy
DestructiveIdempotent

Deploy a Supabase backend from a spec after backend_render: migrations, secrets, auth, legal build, edge functions. Dry-run returns plan; live requires human approval.

Instructions

Deploy the spec's Supabase backend: migrations, secrets, auth, legal build and edge functions (live unless dry_run; needs human approval).

Use when: after backend_render. dry_run=true (default) returns the plan without any call. Not for: single SQL (supabase_run_sql) or one secret (supabase_set_secret). Returns: {ok, plan/steps, dry_run} or an approval_required refusal.

Input Schema

NameRequiredDescriptionDefault
app_dirYesAbsolute path to the app project directory (contains app.spec.json), e.g. /Users/me/Apps/MyApp.
dry_runNoIf true (default) nothing is changed or sent and the exact plan/command is returned; false performs the live action.
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.
project_refYesSupabase project ref to deploy to.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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 / 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 / dry_run / description
      Added value: +"If true (default) nothing is changed or sent and the exact plan/command is returned; false performs the live action."
    • addedInput schema / properties / project_ref / description
      Added value: +"Supabase project ref to deploy to."
  2. First observedv0.1.1

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is partly covered. The description goes further by disclosing the human-approval gate and the approval_required refusal path and the two-call choreography, which are not in the annotations. It stops short of stating what a live run irreversibly changes (e.g. migration/data impact), so not a full 5.

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?

Front-loaded verb+resource, then structured "Use when / Not for / Returns" segments that are scannable. Slightly dense with parentheticals, but every sentence carries actionable information and nothing is 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?

For a destructive, open-world deploy tool with an output schema present, the description covers purpose, sequencing, exclusions, dry-run default, approval flow and refusal shape. Since the return schema exists, the brief "Returns" line is sufficient 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. The description adds meaning the schema does not fully convey: that dry_run=true performs "no call" and that approval_id is threaded from a prior approval_required refusal on a repeat call. That approval round-trip semantics is genuinely beyond the property descriptions.

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 (Deploy) and resource (the spec's Supabase backend) and enumerates the components involved (migrations, secrets, auth, legal build, edge functions). It explicitly distinguishes itself from the SQL and secret siblings by name, so an agent can select it without opening another 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?

Provides explicit sequencing ("Use when: after backend_render"), an explicit exclusion list with named alternatives (supabase_run_sql, supabase_set_secret), and clarifies the dry_run default path. Nothing about when to pick this tool is left to inference.

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