Skip to main content
Glama
Sign In

switch

by ai.switchapp
OverviewDiscussionsAdmin

Apply iPhone Realism

apply_iphone_realism
Read-onlyIdempotent

Phone-shot amateur look — looks like a real person snapped it on their phone. Casual, candid, pore-level real, no professional gloss. Three flavors: digital phone, 35mm film point-and-shoot, or off-duty intimate. Returns the styled prompt stack for your shot and the aspect_ratio to make it at — pair it with generate_image and pass that aspect_ratio along.

Input Schema

NameRequiredDescriptionDefault
styleYesdigital_phone = iPhone main camera snap, 9:16 vertical. film_pointshoot = Contax T2 35mm Portra 400. off_duty_intimate = natural-window editorial candor.
subjectNoWhat you want to shoot. E.g. "a woman walking through a hotel lobby" or "morning coffee on the balcony".
aspect_ratioNoOptional frame shape. Replaces the shape the style uses by default. The answer carries aspect_ratio: pass it to generate_image so the picture is made at that shape.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / aspect_ratio
      Added value: +{
+  "description": "Optional frame shape. Replaces the shape the style uses by default. The answer carries aspect_ratio: pass it to generate_image so the picture is made at that shape.",
+  "enum": [
+    "9:16",
+    "16:9",
+    "1:1",
+    "4:5",
+    "5:4",
+    "3:2",
+    "2:3",
+    "4:3"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / style / description
      Previous value: -"digital_phone = Sony A7IV + 50mm f/1.4 GM phone-style realism. film_pointshoot = Contax T2 35mm Portra 400. off_duty_intimate = natural-window editorial candor."New value: +"digital_phone = iPhone main camera snap, 9:16 vertical. film_pointshoot = Contax T2 35mm Portra 400. off_duty_intimate = natural-window editorial candor."
  2. Changed1 schema field changed
    • changedInput schema / properties / style / description
      Previous value: -"digital_phone = Sony A7IV + 50mm f/1.4 GM phone-style realism. film_pointshoot = Contax T2 35mm Portra 400. off_duty_intimate = Cass Bird natural-window editorial."New value: +"digital_phone = Sony A7IV + 50mm f/1.4 GM phone-style realism. film_pointshoot = Contax T2 35mm Portra 400. off_duty_intimate = natural-window editorial candor."
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive behavior. The description adds useful behavioral context by disclosing that it returns a styled prompt stack plus an aspect_ratio and that this result should be passed to generate_image.

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 compact sentences, front-loaded with the visual effect and followed by the flavor options and integration instruction. No filler or redundant explanation.

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 lightweight style-transform tool with a fully described schema and no output schema, the description is complete: it explains the look, the flavor choices, the returned prompt stack and aspect_ratio, and the downstream generate_image pairing.

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 coverage is 100%, and the schema already explains the style enum values, subject example, and aspect_ratio override behavior. The description names the three flavors and mentions passing aspect_ratio onward, but adds little beyond the structured parameter documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific stylistic transformation: phone-shot amateur realism with three named flavors and a clear contrast to professional gloss. It is easy to distinguish from polished editorial siblings, though it does not explicitly name or route to those alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when the style fits (casual phone-shot look) and explains how to use the returned aspect_ratio with generate_image. It does not explicitly say when to choose this over sibling style tools such as apply_ugc or apply_high_fashion_editorial.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All switch toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources