Skip to main content
Glama

Formstep

by io.github.formstep
OverviewDiscussionsAdmin

Insert table

editor_insertTable

Insert a static content table (text cells) — NOT a question; for rating grids respondents answer, use editor_insertMatrixQuestion. rows and cols are numbers, never strings. Example: {rows:2, cols:2, hasHeader:true, cells:[["Item","Price"],["Visit","40 EUR"]]}.

Input Schema

NameRequiredDescriptionDefault
colsYesNumber of columns (1-10)
rowsYesNumber of rows (1-20)
afterNoNodeId to insert after. Use $prev to chain. Omitting appends to end (usually wrong).
cellsNoCell text, rows x cols, row 0 first, same markup as a paragraph. Omit for an empty grid.
formIdYesForm ID to insert into
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.
hasHeaderNoWhether first row is a header

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / cells / description
      Previous value: -"Cell text, rows x cols, row 0 first. Omit for an empty grid."New value: +"Cell text, rows x cols, row 0 first, same markup as a paragraph. Omit for an empty grid."
  2. Changed1 schema field changed
    • addedInput schema / properties / cells
      Added value: +{
+  "description": "Cell text, rows x cols, row 0 first. Omit for an empty grid.",
+  "items": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "type": "array"
+}
  3. First observed

TDQS

A4.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds the useful distinction that this is static content rather than an interactive question, but says nothing about permissions, reversibility, or insertion side effects. Adequate but not rich given annotations carry the safety burden.

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 tight sentences with the disambiguation front-loaded, followed by a compact example. Every element earns its place; no filler.

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

Completeness5/5

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

For an insert tool with no output schema and annotations covering safety, the description supplies purpose, the sibling alternative, the key type constraint, and a concrete example. Nothing needed to call it correctly is missing.

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 coverage is 100%, so baseline is 3, but the description adds a concrete gotcha ('rows and cols are numbers, never strings') and a full worked example showing the nested cells layout that the schema only describes abstractly. This materially helps correct invocation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 static content table') and immediately disambiguates from the closest sibling by naming editor_insertMatrixQuestion for rating grids. An agent can distinguish this from the many editor_insert* tools without opening the schema.

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

Usage Guidelines5/5

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

Explicitly gives the when ('static content, text cells') and the when-not ('NOT a question; for rating grids...'), and routes to the alternative by name. Nothing about tool selection is left to inference.

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