Skip to main content
Glama
gbatistuta0

AppFactory

by gbatistuta0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Pipeline Mark

pipeline_mark
Idempotent

Set a pipeline stage's status (done, in_progress, pending) in the app manifest to record progress. Marking done runs the stage's enforced gate.

Instructions

Set a pipeline stage's status (done, in_progress, pending) in the app manifest.

Use when: recording progress. Marking done runs the stage's enforced gate. To only test the gate use pipeline_validate. Returns: {ok, stage, status} or a gate refusal.

Input Schema

NameRequiredDescriptionDefault
stageYesPipeline stage id, e.g. 'aso', 'screenshots', 'features' (see pipeline_status for the list).
statusNoNew stage status: 'done', 'in_progress' or 'pending'.done
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. Changed3 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 / stage / description
      Added value: +"Pipeline stage id, e.g. 'aso', 'screenshots', 'features' (see pipeline_status for the list)."
    • addedInput schema / properties / status / description
      Added value: +"New stage status: 'done', 'in_progress' or 'pending'."
  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 declare the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false). The description adds real behavioral context beyond that: marking done triggers the stage's enforced gate, and the call can return a gate refusal. The return-shape sentence is mostly redundant with the output schema but harmless.

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 action, then use-case, alternative, and return shape in four tight sentences with no filler. Every sentence carries information.

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 3-param mutation with 100% schema coverage, an output schema, and full annotations, the description supplies the remaining unknowns: when to call it, which sibling to use instead, and the gate side effect. Nothing needed for correct invocation is missing.

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 stage, status, and app_dir are already fully documented with examples and defaults. The description repeats the status enum values but adds no format or constraint information beyond the schema, so the baseline 3 applies.

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 (Set), resource (a pipeline stage's status), the allowed values, and the storage location (app manifest). It also names the sibling it is not (pipeline_validate), so an agent can separate it from its closest neighbor without opening schemas.

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: recording progress', plus a concrete exclusion with the alternative ('To only test the gate use pipeline_validate'). Both the when and the when-not are present.

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