Skip to main content
Glama

Formstep

by io.github.formstep
OverviewDiscussionsAdmin

Insert date question

editor_insertDateQuestion

Insert a date picker question for date 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
maxDateNoLatest date, YYYY-MM-DD
minDateNoEarliest date, YYYY-MM-DD
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 / maxDate
      Added value: +{
+  "description": "Latest date, YYYY-MM-DD",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}
    • addedInput schema / properties / minDate
      Added value: +{
+  "description": "Earliest date, YYYY-MM-DD",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}
  2. First observed

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already state readOnlyHint=false, destructiveHint=false, openWorldHint=false, giving the safety profile. The description adds no further behavioral context (such as ordering behavior, side effects, or required permissions) beyond the one-sentence purpose, so it contributes little beyond 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.

Conciseness3/5

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

The description is a single grammatical sentence with no filler, but for a 9-parameter insertion tool it is arguably too terse and does not front-load any operational guidance. It is concise but under-specified for the tool's complexity.

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

Completeness2/5

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

Given 9 parameters, many sibling tools that insert other question types, and no output schema, the description is not complete enough. It fails to help the agent distinguish this tool from other insert-question tools or understand when to use it, though annotations and schema cover safety and parameters.

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 9 parameters are documented in the schema itself. The description adds no parameter-level information, leaving the schema to carry the full semantic load; baseline 3 is appropriate.

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 names a specific verb ('Insert') and resource ('date picker question'), making the tool's function clear. It does not differentiate from sibling insert-question tools (e.g., insertTimeQuestion, insertScheduleAppointmentQuestion), so it stops short of a 5.

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?

No when-to-use guidance, no prerequisites, and no alternatives are mentioned. The agent receives no help choosing this tool over other question-insertion tools.

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