Skip to main content
Glama

Formstep

by io.github.formstep
OverviewDiscussionsAdmin

Insert picture choice question

editor_insertPictureChoiceQuestion

Insert a picture choice question. Use when choices are inherently visual (products, designs, photos). Example: {title:"Pick a style", images:[{label:"Modern", src:"https://…"}]}. Use images the user uploaded or URLs they provided — never invent or guess image URLs.

Input Schema

NameRequiredDescriptionDefault
afterNoNodeId to insert after. Use $prev to chain. Omitting appends to end (usually wrong).
titleYesQuestion title
formIdYesForm ID to insert into
imagesYesPicture choices with images
isHiddenNoStart hidden (the target of a `show` rule).
multipleNoAllow multiple selections
parentIdNoParent node ID to insert into (e.g., column1)
positionNoPosition among siblings: inside parentId when given, else at the top level ('first' = top of the form, e.g. a title). Not combinable with after.
requiredNoWhether question is required. Default: true. Pass false to make the field optional.
maxSelectionsNoMost pictures to pick (multiple only)
minSelectionsNoFewest pictures to pick (multiple only)
defaultOptionsNoLabels preselected; one at most unless multiple

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / defaultOptions
      Added value: +{
+  "description": "Labels preselected; one at most unless multiple",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / maxSelections
      Added value: +{
+  "description": "Most pictures to pick (multiple only)",
+  "minimum": 0,
+  "type": "integer"
+}
    • addedInput schema / properties / minSelections
      Added value: +{
+  "description": "Fewest pictures to pick (multiple only)",
+  "minimum": 0,
+  "type": "integer"
+}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare write (readOnlyHint=false), non-destructive, closed-world. The description adds genuinely new behavioral guidance beyond that: images must come from user uploads or provided URLs, and the anti-hallucination constraint "never invent or guess image URLs." It doesn't cover permissions or how insertion placement behaves, keeping it at 4.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four tightly packed sentences: purpose, when-to-use, a minimal example, and a constraint. Front-loaded and free of filler; the example is compact and the final sentence earns its place as a safety rule.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 12-parameter insertion tool with full schema coverage, no output schema, and safety annotations, the description covers purpose, selection criterion, input shape, and the key image-sourcing constraint. Placement/chaining behavior is left entirely to the schema, which is acceptable given its coverage.

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 schema already documents all 12 parameters including after/position/parentId placement semantics. The inline example lightly reinforces the title/images shape, and the image-source rule adds meaning for src, but this is baseline-plus rather than substantial new parameter insight.

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 ("Insert a picture choice question") and adds the discriminating condition "when choices are inherently visual (products, designs, photos)," which separates it from the many sibling insert*Question tools. An agent can pick this over insertRadioQuestion/insertSelectQuestion without opening a schema.

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

Usage Guidelines4/5

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

Gives a clear when-to-use criterion ("choices are inherently visual") and a concrete example context ("Pick a style"). It stops short of naming the non-visual alternatives or stating when-not to use it, so it's clear context rather than a full routing rule.

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

All Formstep 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