Skip to main content
Glama
gbatistuta0

AppFactory

by gbatistuta0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Screenshot Onboarding Heroes

screenshot_onboarding_heroes

Generate fal.ai hero images for each legacy onboarding step (onb_step0..N); requires allow_external_generator=true and returns image paths or a refusal.

Instructions

LEGACY, opt-in: generate fal hero images per onboarding step (onb_step0..N).

Use when: only for a legacy hero-image onboarding. Onboarding visuals normally come from Claude Design boards. Requires allow_external_generator=true. Returns: {ok, images: [paths]} or a refusal.

Input Schema

NameRequiredDescriptionDefault
countNoNumber of onboarding hero images to generate (default 11).
app_dirYesAbsolute path to the app project directory (contains app.spec.json), e.g. /Users/me/Apps/MyApp.
conceptYesShort concept description of the app used to write the image prompt, e.g. 'AI pet portrait maker'.
allow_external_generatorNoMust be true to allow the paid fal.ai image generator; default false refuses.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.5
    • addedInput schema / properties / allow_external_generator / description
      Added value: +"Must be true to allow the paid fal.ai image generator; default false refuses."
    • 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 / concept / description
      Added value: +"Short concept description of the app used to write the image prompt, e.g. 'AI pet portrait maker'."
    • addedInput schema / properties / count / description
      Added value: +"Number of onboarding hero images to generate (default 11)."
  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 cover the safety profile (readOnly=false, openWorld=true, destructive=false), and the description adds genuinely new context: it is legacy/opt-in, invokes a paid fal.ai generator, and returns a refusal when allow_external_generator is not set. It does not, however, discuss cost magnitude, latency, or overwrite behavior for existing hero images.

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 short blocks — status, usage condition, return shape — with the LEGACY warning front-loaded. Every sentence carries distinct information and nothing is repeated.

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 4-parameter tool with full schema coverage and an output schema, the description supplies the missing decision-relevant context: deprecation status, the external-generator gate, and the refusal outcome. Nothing needed to call it correctly is absent.

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 the baseline is 3. The description reinforces the onb_step0..N mapping and the allow_external_generator gate but adds no syntax or format detail beyond what the schema already documents.

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 ('generate fal hero images per onboarding step') plus the onb_step0..N scope, and flags itself as LEGACY, which cleanly separates it from design_generate and screenshot_generate_sample. An agent can identify the operation and its status 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?

Explicit 'Use when: only for a legacy hero-image onboarding' plus the counter-guidance that onboarding visuals normally come from Claude Design boards routes the agent away by default. The prerequisite allow_external_generator=true is also stated outright.

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