Skip to main content
Glama

Formstep

by io.github.formstep
OverviewDiscussionsAdmin

Insert matrix question

editor_insertMatrixQuestion

Insert a matrix/grid question. Use when rating multiple items on the same scale. Requires rows and columns as native string arrays (never a JSON string). Example: {title:"Rate our service", rows:["Speed","Quality"], columns:["Poor","OK","Great"]}.

Input Schema

NameRequiredDescriptionDefault
rowsYesRow labels
afterNoNodeId to insert after. Use $prev to chain. Omitting appends to end (usually wrong).
titleYesQuestion title
formIdYesForm ID to insert into
columnsYesColumn labels
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.
requireAllRowsNoEvery row needs an answer
minAnsweredRowsNoFewest rows to answer

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / minAnsweredRows
      Added value: +{
+  "description": "Fewest rows to answer",
+  "minimum": 0,
+  "type": "integer"
+}
    • addedInput schema / properties / requireAllRows
      Added value: +{
+  "description": "Every row needs an answer",
+  "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 a non-read-only, non-destructive, closed-world write, so the safety profile is covered. The description adds the useful input constraint that rows/columns must be native arrays and never a JSON string, but says nothing about insertion placement behavior, auth, or side effects beyond what annotations provide.

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?

Three sentences, front-loaded with the purpose before the usage note and format constraint. The example is somewhat long for an inline snippet but directly reduces malformed calls, so it earns its place.

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 an 11-parameter insertion tool with full schema coverage, no output schema, and pre-populated annotations, the description covers purpose, use case, and the highest-risk input format pitfall. Placement semantics are left entirely to the schema, which is a minor gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3, but the description earns extra credit by calling out the native-array requirement for rows/columns and providing a concrete payload example. It does not clarify the placement parameters (after/position/parentId), which remain schema-only.

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 matrix/grid question') and adds a scope note ('rating multiple items on the same scale') that separates it from editor_insertRatingQuestion and editor_insertRadioQuestion. It does not name siblings explicitly, so it stays 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 Guidelines4/5

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

'Use when rating multiple items on the same scale' gives a clear use context. It lacks any when-not guidance or explicit pointer to the alternative question types an agent might confuse it with, but the context is unambiguous.

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