Skip to main content
Glama

formbase (formbase.so)

by io.github.formbaseso
OverviewDiscussionsAdmin

Insert repeating group

editor_insertRepeatingGroup

Insert a repeating group: a labeled block of member fields the respondent can add multiple instances of (e.g. "Who is coming?" repeated per guest, each with Name + Phone). Provide the group name and 1+ member fields — a group is auto-deleted if it has no fields, so it must be born with at least one. Member types: text, number, date, time, email, phone, url, radio, checkbox, select, switch, rating (choice types need options). Add other/complex member types AFTER creation with the normal editor_insert*Question tools, passing parentId = the group id. Both the whole-group id (renders every instance inline, e.g. "Alice - 111, Bob - 222") and each member field id can be @-mentioned in body text, emails, and PDFs. Returns members — one { nodeId, title, inputId, options } per member field, in order — so logic and updates can target them without editor_getDocument.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesGroup label shown above the block, e.g. "Guests" or "Who is coming?".
afterNoNodeId to insert after. Use $prev to chain. Omitting appends to end (usually wrong).
fieldsYesMember fields repeated together per instance. At least one — an empty group is auto-deleted.
formIdYesForm ID to insert into
addButtonLabelNoLabel for the "add another" button. Default: "Add".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations only declare the write/non-destructive/openWorld profile, so the description carries the rest: the auto-deletion of empty groups, the @-mention behavior for whole-group and member ids, and the exact return payload. This is substantial beyond annotations, though permission/auth context is not covered.

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?

Dense but fully front-loaded: the definition comes first, then the constraint, then member types, then the sibling routing, then the return shape. Every sentence conveys operational information with 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 a non-trivial creation tool with no output schema, the description supplies the return structure (members with nodeId/title/inputId/options), the deletion edge case, and downstream id usage, so an agent has everything needed to call and chain it correctly.

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 practical meaning: fields must be ≥1, choice types need options, and the group and member ids are addressable in body/email/PDF. It explains why parameters matter, not just what they are.

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 repeating group) and immediately distinguishes it from siblings by defining the concept with a concrete example. It also names the sibling family (editor_insert*Question) that handles the cases this tool does not, so an agent can disambiguate without opening a 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?

Explicit routing: use this for member types text/number/date/etc. at creation, and add other/complex member types AFTER creation via editor_insert*Question with parentId = the group id. The 'must be born with at least one field or it is auto-deleted' rule gives a clear precondition.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All formbase (formbase.so) 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