Superforms

Create Superforms Ask

create_ask

Create a voice-first Superforms answer link for human input. Backward-compatible alias for create_form.

Input Schema

TableJSON Schema

Name	Required	Description
`goal`	No
`title`	No
`prompt`	No	Plain-English ask or request. Use only when explicit questions are not already known.
`context`	No	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.
`questions`	No	Explicit questions to ask the respondent. Use this whenever questions already exist; preserve them exactly.
`persistent`	No
`followUpMode`	No	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.
`responseMode`	No
`responseLimit`	No	Use "one" for a form intended for one named person/client. Use "multiple" for forms, surveys, feedback, customers, users, and public/embedded links.
`questionContext`	No
`creationSessionUrl`	No
`max_total_questions`	No	Optional compatibility setting. Omit for adaptive one-question smart follow-ups.
`max_followups_per_question`	No	Optional compatibility setting. Omit for adaptive one-question smart follow-ups.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed5 schema fields changedJul 31, 2026

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"
+  }
+]

Changed1 schema field changedJun 25, 2026

addedInput schema / properties / responseLimit

Added value: +{
+  "description": "Use \"one\" for a form intended for one named person/client. Use \"multiple\" for forms, surveys, feedback, customers, users, and public/embedded links.",
+  "enum": [
+    "one",
+    "multiple"
+  ],
+  "type": "string"
+}

Changed2 schema fields changedJun 12, 2026

addedInput schema / properties / max_followups_per_question

Added value: +{
+  "description": "Maximum AI follow-up questions per specified question. Use 1 for optional specified-question follow-ups.",
+  "type": "number"
+}

addedInput schema / properties / max_total_questions

Added value: +{
+  "description": "Total question safety cap. Use 20 for open-ended feedback conversations.",
+  "type": "number"
+}

First observedJun 6, 2026

TDQS

C2.7/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. It mentions 'voice-first' and 'answer link' as behavioral traits, but does not disclose what happens upon creation, any side effects, permission requirements, or the return format. The alias reference hints at behavior but does not explain it.

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?

The description is a single concise sentence that front-loads the core purpose. It is not verbose and every word adds some intent. However, it is arguably under-specified rather than appropriately concise, which is a minor flaw.

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 the tool's complexity (13 parameters, nested question objects, no output schema, no annotations), the description is grossly incomplete. It does not explain return values, side effects, or how the parameters interact, and the alias reference is not elaborated. This is inadequate for an agent to invoke the tool correctly.

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

Parameters2/5

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

Schema description coverage is only 54%, with several parameters (goal, title, persistent, responseMode, questionContext, creationSessionUrl) lacking descriptions. The tool description itself adds no parameter-level semantics beyond 'voice-first', which loosely relates to responseMode. It fails to compensate for the schema 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 'Create' and the resource 'voice-first Superforms answer link for human input', and explicitly identifies itself as a backward-compatible alias for create_form. This distinguishes it from the other sibling tools like create_feedback_form, though the phrase 'human input' is somewhat vague.

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?

The description mentions that it is an alias for create_form, which implies similar usage, but provides no explicit guidance on when to use this tool versus the alternatives (e.g., create_form or create_feedback_form). There are no stated prerequisites, exclusions, or context for when this alias should be preferred.

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

All Superforms tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.2/5.0

Disambiguation3/5

There is clear overlap between several tools: create_ask is explicitly a backward-compatible alias for create_form, making them nearly indistinguishable. get_my_form_responses vs get_responses and watch_my_form_responses vs watch_ask also serve similar purposes with only subtle differences (form ownership vs generic ask). The creation session tools (join_creation_session, update_creation_session) and creation tools (create_form, create_feedback_form) have moderately clear boundaries but could confuse agents about when to use session tools vs direct creation.

Naming Consistency3/5

The naming mostly follows a verb_noun pattern (create_form, list_asks, watch_ask) and many share a consistent 'my_' prefix for owned resources. However, the aliasing (create_ask), the distinction between 'ask' and 'form' terminology, and create_feedback_form vs create_form introduce inconsistency in domain vocabulary. Watch_ask vs watch_my_form_responses and get_responses vs get_my_form_responses use parallel but not fully consistent naming.

Tool Count4/5

11 tools is a reasonable count for a form lifecycle server. However, three tools are essentially redundant aliases or near-duplicates (create_ask, get_responses, and possibly watch_ask given HTTP bridge equivalents), which could be consolidated. The count is not excessive or too thin, but the effective surface is smaller than 11 distinct tools.

Completeness3/5

The server covers creation (create_form, create_feedback_form), listing (list_asks, list_my_forms), reading responses (get_responses, get_my_form_responses), and real-time watching (watch_ask, watch_my_form_responses). However, there is no tool for updating or deleting existing forms, and no tool for closing/archiving a form. The creation-session tools are present but lack a corresponding read/view for drafts. The domain is form lifecycle, and update/delete operations for published forms are notable gaps.

Resources

Need Help?