Skip to main content
Glama

Formstep

by io.github.formstep
OverviewDiscussionsAdmin

Insert time question

editor_insertTimeQuestion

Insert a time picker question for time selection.

Input Schema

NameRequiredDescriptionDefault
afterNoNodeId to insert after. Use $prev to chain. Omitting appends to end (usually wrong).
titleYesQuestion title
formIdYesForm ID to insert into
maxTimeNoLatest time, HH:mm
minTimeNoEarliest time, HH:mm
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / maxTime
      Added value: +{
+  "description": "Latest time, HH:mm",
+  "pattern": "^([01]\\d|2[0-3]):([0-5]\\d)$",
+  "type": "string"
+}
    • addedInput schema / properties / minTime
      Added value: +{
+  "description": "Earliest time, HH:mm",
+  "pattern": "^([01]\\d|2[0-3]):([0-5]\\d)$",
+  "type": "string"
+}
  2. First observed

TDQS

C2.9/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 known. The description adds nothing beyond that: it doesn't say the insert mutates the form structure, where the new node lands, or what a failure looks like. All placement behavior lives only in the schema.

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?

A single short, front-loaded sentence with no filler. It is efficient, though the brevity borders on under-specification rather than true conciseness.

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

Completeness3/5

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

Given nine parameters, a large sibling set, and no output schema, the description is thin — it never mentions placement (after/parentId/position) or that this is a structural mutation of the form. The rich parameter schema and the annotations cover most of the gap, keeping it at minimum-viable rather than inadequate.

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%, including useful notes on 'after', 'position' and 'isHidden', so the schema does the heavy lifting. The description contributes no parameter meaning of its own, which is exactly the baseline-3 case for high coverage.

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 and resource: 'Insert a time picker question', which is enough to distinguish it from the many sibling insert*Question tools (e.g. editor_insertDateQuestion). It stops short of naming an explicit contrast, but the resource noun is unambiguous.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites (e.g. that the form must exist / be editable), and no mention of alternatives such as editor_insertDateQuestion. The agent gets no help choosing this over its 30+ sibling insert tools beyond the word 'time'.

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