elicitation-workflows

Structured user input during MCP tool execution is collected using schema-driven elicitation forms. You define primitive schema types like String, Number, Boolean, and Enum, then prompt clients via an ElicitationProvider to gather validated responses across single or multi-step workflows.

Schema-driven elicitation is a mechanism that requests predefined, structured input from clients during tool execution. You need it for multi-step workflows to collect consistent data across sessions, reducing ad-hoc gathering through composite forms with built-in validation and session state.

Build an elicitation request using ElicitationBuilder::new to define your message and schema. The framework applies built-in validation for required fields, primitive type checks, and simple constraints, ensuring data integrity before the structured input is processed.

Yes, you can plug in custom user interfaces via the ElicitationProvider interface. The framework supports both mock providers for testing and production providers, allowing you to implement elicitation for CLI, web, or custom UI environments.

Dynamic schema creation at runtime is supported through DynamicElicitation and ElicitCreateRequest components. This allows you to dynamically generate schema-driven forms and prompt for structured input during MCP tool execution, adapting to varying context requirements.

Primitive schema types are limited to String, Number, Boolean, and Enum with validation for required fields, types, and simple constraints. Complex nested data structures require optional dynamic validation, as the built-in validation only covers basic primitive type checks.