Skip to main content
Glama

Formstep

by io.github.formstep
OverviewDiscussionsAdmin

Insert checkbox question

editor_insertCheckboxQuestion

Insert a checkbox question for multi-choice selection. Requires 1+ options. Use when user can pick multiple.

Input Schema

NameRequiredDescriptionDefault
afterNoNodeId to insert after. Use $prev to chain. Omitting appends to end (usually wrong).
titleYesQuestion title
formIdYesForm ID to insert into
optionsYesCheckbox options (minimum 1, non-empty, unique)
isHiddenNoStart hidden (the target of a `show` rule).
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 options to pick
minSelectionsNoFewest options to pick
defaultOptionsNoLabels of the options checked by default
randomizeOptionsNoShuffle option order per respondent

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / defaultOptions
      Added value: +{
+  "description": "Labels of the options checked by default",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / maxSelections
      Added value: +{
+  "description": "Most options to pick",
+  "minimum": 0,
+  "type": "integer"
+}
    • addedInput schema / properties / minSelections
      Added value: +{
+  "description": "Fewest options to pick",
+  "minimum": 0,
+  "type": "integer"
+}
    • addedInput schema / properties / randomizeOptions
      Added value: +{
+  "description": "Shuffle option order per respondent",
+  "type": "boolean"
+}
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive write, so the safety profile is covered. The description's main behavioral claim, "Requires 1+ options," merely restates the schema's minItems constraint and adds no new mutation context. No mention of ordering effects or side effects on existing nodes.

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, front-loaded sentences with zero filler. The core purpose and the key usage condition lead, and no sentence is redundant.

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 mutation tool with full schema coverage and clear annotations, the definition supplies enough to act on. The absence of output-schema detail is acceptable, though the description could note insertion/ordering caveats that the schema only partially conveys.

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 12 parameters are already documented in the schema (including the subtle 'after' vs 'position' semantics and the required-default). The description adds no parameter detail beyond the "1+ options" restatement, which is the baseline 3 case.

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?

The description gives a specific verb and resource ("Insert a checkbox question") and frames it as "multi-choice selection," which separates it from single-choice siblings like editor_insertRadioQuestion. It does not explicitly name the contrasting sibling, so the differentiation must be inferred from "multi-choice."

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?

"Use when user can pick multiple" gives a clear condition for selecting this tool over its alternatives. It stops short of naming the sibling to use for single-choice cases, so the exclusion is only implied.

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