Skip to main content
Glama
gbatistuta0

AppFactory

by gbatistuta0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Screenshot Capture

screenshot_capture
Idempotent

Capture a single raw screenshot from a booted simulator and save it to marketing/raw// for localized app store assets.

Instructions

Capture a raw screenshot from the booted simulator into marketing/raw//.png.

Use when: capturing a single screen manually. For the full localized set use screenshot_build_all. Returns: {ok, path}.

Input Schema

NameRequiredDescriptionDefault
nameYesScreen name, used as the file name, e.g. 'paywall'.
udidYesSimulator UDID from build_list_simulators, e.g. 'A1B2C3D4-...'.
localeYesApp locale of the capture, e.g. 'en-US'; used as the output subfolder.
marketing_dirYesPath to the app's marketing/ directory.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.5
    • addedInput schema / properties / locale / description
      Added value: +"App locale of the capture, e.g. 'en-US'; used as the output subfolder."
    • addedInput schema / properties / marketing_dir / description
      Added value: +"Path to the app's marketing/ directory."
    • addedInput schema / properties / name / description
      Added value: +"Screen name, used as the file name, e.g. 'paywall'."
    • addedInput schema / properties / udid / description
      Added value: +"Simulator UDID from build_list_simulators, e.g. 'A1B2C3D4-...'."
  2. First observedv0.1.1

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the mutation and repeat-safety profile is covered. The description adds the output destination convention, but does not mention that an existing file at the same path is overwritten (implied by idempotentHint) or any prerequisites such as the simulator needing to be booted.

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 lines with the action, the condition, and the return value front-loaded. 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?

An output schema exists, so return-value detail is not the description's burden, and annotations carry the safety profile. Combined with a fully documented parameter schema and a clear alternative tool pointer, an agent has everything needed to invoke this 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 are already documented in the schema, and a baseline of 3 applies. The description adds modest value by showing how 'locale' and 'name' compose into the output path, but it introduces no format or constraint detail beyond that.

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 (capture) and resource (raw screenshot) and pins the artifact to a concrete output path pattern 'marketing/raw/<locale>/<name>.png'. It is clearly distinguishable from siblings like screenshot_build_all and screenshot_brand.

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?

Explicitly states the triggering condition ('capturing a single screen manually') and names the alternative for the contrasting case ('For the full localized set use screenshot_build_all'). This is textbook when/when-not plus alternative routing.

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