Skip to main content
Glama

Formstep

by io.github.formstep
OverviewDiscussionsAdmin

Insert radio question

editor_insertRadioQuestion

Insert a radio button question for single-choice selection. Requires 2+ options. Use when user must pick exactly one.

Input Schema

NameRequiredDescriptionDefault
afterNoNodeId to insert after. Use $prev to chain. Omitting appends to end (usually wrong).
titleYesQuestion title
formIdYesForm ID to insert into
optionsYesRadio options (minimum 2, 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.
defaultOptionNoLabel of the option preselected
randomizeOptionsNoShuffle option order per respondent

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / defaultOption
      Added value: +{
+  "description": "Label of the option preselected",
+  "type": "string"
+}
    • 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 readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description only restates the 2+ option constraint that the schema already enforces and adds nothing about insertion placement or effects on existing nodes, which is the real behavioral risk for an insert tool.

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 no filler; the core purpose, constraint, and selection criterion are all delivered immediately.

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?

With 100% schema coverage, no output schema, and annotations covering safety, the description covers what an agent needs to select the tool. The main omission is any guidance on the positioning parameters (after/parentId/position) that make an insert call succeed, but those are fully documented in the schema.

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%, so all ten parameters including after/parentId/position are fully documented in the schema; baseline is 3. The description adds no syntax or format meaning beyond the schema, only echoing the minimum-options rule.

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 verb (Insert) and resource (radio button question) plus the semantics (single-choice selection). However, it never names or contrasts the many sibling question-insertion tools (checkbox, select, picture choice, switch) that also create choice-based questions, so differentiation is left to inference.

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 must pick exactly one" gives a clear positive usage cue and implicitly excludes multi-select tools like editor_insertCheckboxQuestion. It stops short of explicitly naming the alternative or stating when-not conditions.

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