Elicitly Pro

Ask the user to fill a form

elicit_form

Trigger a form elicitation with a caller-supplied JSON schema; returns the raw {action, content}. For a plain OK/Cancel question, prefer elicit_confirm. MUST NOT be used to request secrets, credentials, or other sensitive information.

Input Schema

TableJSON Schema

Name	Required	Description
`message`	Yes	The instruction shown to the user above the form fields.
`timeoutSeconds`	No	How long to wait for the answer, in seconds (default 300, clamped 60-3600) — raise it for forms with several fields.
`requestedSchema`	Yes	JSON Schema for the form, restricted to the MCP elicitation requestedSchema subset: a flat object whose properties are strings, numbers/integers, booleans, or enums — no nested objects, arrays of objects, $ref, or allOf. See https://modelcontextprotocol.io/specification/2025-11-25/client/elicitation#requested-schema

Output Schema

TableJSON Schema

Name	Required	Description	Default
`action`	Yes	accept = the user submitted the form; decline = an explicit no; cancel = dismissed unanswered (including timeout); error = the elicitation failed.
`content`	Yes	On accept, the submitted values keyed by requestedSchema property name; null for every other action.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 8, 2026
- changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +{}
```

Changed4 schema fields changedSep 5, 2026

addedInput schema / properties / message / description

Added value: +"The instruction shown to the user above the form fields."

addedInput schema / properties / requestedSchema / description

Added value: +"JSON Schema for the form, restricted to the MCP elicitation requestedSchema subset: a flat object whose properties are strings, numbers/integers, booleans, or enums — no nested objects, arrays of objects, $ref, or allOf. See https://modelcontextprotocol.io/specification/2025-11-25/client/elicitation#requested-schema"

addedInput schema / properties / timeoutSeconds / description

Added value: +"How long to wait for the answer, in seconds (default 300, clamped 60-3600) — raise it for forms with several fields."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "action": {
+      "description": "accept = the user submitted the form; decline = an explicit no; cancel = dismissed unanswered (including timeout); error = the elicitation failed.",
+      "enum": [
+        "accept",
+        "decline",
+        "cancel",
+        "error"
+      ],
+      "type": "string"
+    },
+    "content": {
+      "anyOf": [
+        {
+          "additionalProperties": {},
+          "propertyNames": {
+            "type": "string"
+          },
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "On accept, the submitted values keyed by requestedSchema property name; null for every other action."
+    }
+  },
+  "required": [
+    "action",
+    "content"
+  ],
+  "type": "object"
+}

First observedSep 4, 2026

TDQS

Score is being calculated.

All Elicitly Pro tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?