Skip to main content
Glama
gbatistuta0

AppFactory

by gbatistuta0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Icon Install

icon_install
Idempotent

Installs the 1024x1024 design icon master into AppIcon.appiconset after export and upload, flattening alpha and writing a verification file for the icon gate.

Instructions

Install the Claude Design app icon (1024x1024 master) into AppIcon.appiconset and write .appfactory/verify/icon.json.

Use when: after design_export_png produced design/icon.png and design_record_upload recorded the upload; the icon gate requires it. Alpha is flattened. Returns: {ok, icon, marker} or an error naming the missing/invalid master.

Input Schema

NameRequiredDescriptionDefault
sourceNoPath to the 1024x1024 icon master, relative to the app dir (default 'design/icon.png').design/icon.png
app_dirYesAbsolute path to the app project directory (contains app.spec.json), e.g. /Users/me/Apps/MyApp.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 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 / source / description
      Added value: +"Path to the 1024x1024 icon master, relative to the app dir (default 'design/icon.png')."
  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 safety profile (idempotentHint=true, destructiveHint=false, non-open-world), and the description adds real behavioral detail beyond them: alpha is flattened, a marker file is written, and failures name the missing/invalid master. It stops short of describing overwrite semantics for an existing appiconset, which is the one mutation detail left unstated.

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 labeled segments ('Use when:' / 'Returns:') keep preconditions, effects, and outputs front-loaded and scannable, with no filler sentences.

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 two-parameter install step, the description plus annotations plus existing output schema cover everything needed to invoke correctly: preconditions, side effects, and failure mode are all present.

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 both parameters (source and app_dir) are already fully documented with defaults and formats; the baseline of 3 applies. The description only indirectly hints at the source path via the design_export_png reference and adds no syntax beyond 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 pair ('Install the Claude Design app icon ... into AppIcon.appiconset') plus a secondary artifact it writes (verify/icon.json). It is clearly distinguishable from icon_generate (produces) and design_export_png (exports the PNG consumed here).

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?

The 'Use when:' clause names the exact upstream preconditions (design_export_png produced design/icon.png, design_record_upload recorded the upload) and the gating rule ('the icon gate requires it'), so the agent knows precisely when to reach for this tool.

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