Skip to main content
Glama

Superforms

by co.superforms
OverviewDiscussionsAdmin

Create Superforms Form

create_form

Publish a voice-first form link immediately after creator confirmation, collect human answers, and pipe responses back to the agent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
goalNo
titleNo
promptNoPlain-English ask or request. Use only when explicit questions are not already known.
contextNoPrivate context for smart follow-ups. Summarize relevant non-sensitive host-conversation context and append any extra context the creator provides. Never shown to respondents.
questionsNoExplicit questions to ask the respondent. Use this whenever questions already exist; preserve them exactly.
persistentNo
followUpModeNoFor exactly one question, set this only after asking the creator "Want smart follow-up questions?" Use deep_dive for yes or none for no. For multiple questions, use none unless explicitly requested.
responseModeNo
responseLimitNoUse "one" for a form intended for one named person/client. Use "multiple" for forms, surveys, feedback, customers, users, and public/embedded links.
questionContextNo
creationSessionUrlNo
max_total_questionsNoOptional compatibility setting. Omit for adaptive one-question smart follow-ups.
max_followups_per_questionNoOptional compatibility setting. Omit for adaptive one-question smart follow-ups.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / context / description
      Previous value: -"Hidden context for the form."New value: +"Private context for smart follow-ups. Summarize relevant non-sensitive host-conversation context and append any extra context the creator provides. Never shown to respondents."
    • addedInput schema / properties / followUpMode / description
      Added value: +"For exactly one question, set this only after asking the creator \"Want smart follow-up questions?\" Use deep_dive for yes or none for no. For multiple questions, use none unless explicitly requested."
    • changedInput schema / properties / max_followups_per_question / description
      Previous value: -"Maximum AI follow-up questions per specified question. Use 1 for optional specified-question follow-ups."New value: +"Optional compatibility setting. Omit for adaptive one-question smart follow-ups."
    • changedInput schema / properties / max_total_questions / description
      Previous value: -"Total question safety cap. Use 20 for open-ended feedback conversations."New value: +"Optional compatibility setting. Omit for adaptive one-question smart follow-ups."
    • changedInput schema / properties / questions / items / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "context": {
-        "type": "string"
-      },
-      "id": {
-        "type": "string"
-      },
-      "text": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "text"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "maxLength": 200,
+    "minLength": 1,
+    "type": "string"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "context": {
+        "type": "string"
+      },
+      "id": {
+        "type": "string"
+      },
+      "text": {
+        "maxLength": 200,
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "required": [
+      "text"
+    ],
+    "type": "object"
+  }
+]
  2. Added

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description is a single sentence that conveys the high-level lifecycle ('publish', 'collect', 'pipe back') but omits material behaviors: that confirmation from the creator is a prerequisite step, that the form is voice-first by default, potential side effects like creating a persistent shareable link, or any rate limits/authorization requirements. With 13 parameters and no annotations, this level of transparency is insufficient.

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 concise sentence that front-loads the primary purpose well. However, for a 13-parameter tool with complex workflow semantics and no annotations, the brevity works against it — it fails to earn its space by covering the important operational details that an agent needs to invoke it correctly. Being too short is a deficiency, not a virtue, in this context.

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?

With 13 parameters, no annotations, no output schema, nested objects, and 46% of parameters undocumented in the schema, the description is far too thin. The confirmation-workflow prerequisite, the voice-first nature, the 'smart follow-ups' semantics present in the schema, and the distinction from similar creation tools are all absent. The single sentence provides only the most surface-level picture and is inadequate for correct invocation of this complex tool.

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 coverage is 54%, and 6 of 13 parameters lack descriptions (goal, title, persistent, responseMode, questionContext, creationSessionUrl). The description itself adds NO parameter-level information whatsoever — it is entirely about the tool's overall function. The schema does have useful guidance for key params (questions, followUpMode, responseLimit), but the uncovered parameters remain undocumented by both schema and description, and the description doesn't compensate for those gaps.

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 clearly states the verb ('Publish a voice-first form link') and the resource ('form'), and its outcome ('collect human answers, pipe responses back to agent'). It distinguishes itself as a 'voice-first' form creation tool among siblings, and implies the confirmation/approval workflow. However, it does not explicitly contrast with sibling tools like create_ask or create_feedback_form, leaving some ambiguity about when each is preferred.

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?

The description provides clear context on the workflow: 'immediately after creator confirmation' and 'pipe responses back to the agent'. This gives the agent a sense of when the tool is intended to be invoked. However, it gives no explicit when-not-to-use guidance or named alternatives (e.g., when to prefer create_ask or create_feedback_form instead), leaving the agent to infer boundaries among sibling tools.

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

All Superforms toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources