Skip to main content
Glama

Formstep

by io.github.formstep
OverviewDiscussionsAdmin

Insert text question

editor_insertTextQuestion

Insert a text question for short or long text responses. Use for names, comments, descriptions.

Input Schema

NameRequiredDescriptionDefault
maxNoMaximum character length
minNoMinimum character length
afterNoNodeId to insert after. Use $prev to chain. Omitting appends to end (usually wrong).
titleYesQuestion title
formIdYesForm ID to insert into
patternNoRegex the answer must match; anchor with ^ $.
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.
multilineNoAllow multiline input (textarea)
placeholderNoPlaceholder text
defaultValueNoLiteral default seeded on open; respondent can edit or clear it. Not with defaultValueFieldRef.
defaultValueFieldRefNoPre-fill the input with a hidden or calculated field value at fill time. The respondent can still edit it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / pattern
      Added value: +{
+  "description": "Regex the answer must match; anchor with ^ $.",
+  "minLength": 1,
+  "type": "string"
+}
  2. First observed

TDQS

B3.4/5.0
Behavior2/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 adds nothing behavioral beyond content type—no mention of side effects, ordering constraints on the form tree, or what inserting does to existing elements—so it earns little credit above the annotations.

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?

Two short sentences, front-loaded, with zero filler. Every clause earns its place by naming the field type and typical uses.

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 14-param insertion tool with full schema coverage and no output schema, the schema carries the mechanical burden, so the description needn't explain parameters. Its main gap is distinguishing this tool from the many sibling question-insertion tools, which the description only partially does by content type.

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% and 14 params are thoroughly documented, including subtle placement semantics (after, position, parentId) and defaults. The description contributes no parameter-level meaning, so the baseline 3 applies.

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+resource ('Insert a text question') and scopes the response type ('short or long text responses'). It partially differentiates from sibling question types by content type, but never names the alternatives (e.g. editor_insertParagraph, editor_insertSelectQuestion) that an agent must choose between.

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?

'Use for names, comments, descriptions' gives implied usage context for free-text fields. However, it offers no when-not-to-use guidance and no explicit routing among the ~35 sibling insert tools, leaving the agent to infer that this is for free text rather than select, paragraph, or other field types.

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