You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/concepts/elicitation/elicitation.md
+8-1Lines changed: 8 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,9 +16,16 @@ The C# SDK registers an instance of <xref:ModelContextProtocol.Server.McpServer>
16
16
so tools can simply add a parameter of type <xref:ModelContextProtocol.Server.McpServer> to their method signature to access it.
17
17
18
18
The MCP Server must specify the schema of each input value it is requesting from the user.
19
-
Only primitive types (string, number, boolean) are supported for elicitation requests.
19
+
Primitive types (string, number, boolean) and enum types are supported for elicitation requests.
20
20
The schema may include a description to help the user understand what is being requested.
21
21
22
+
For enum types, the SDK supports several schema formats:
23
+
-**UntitledSingleSelectEnumSchema**: A single-select enum where the enum values serve as both the value and display text
24
+
-**TitledSingleSelectEnumSchema**: A single-select enum with separate display titles for each option (using JSON Schema `oneOf` with `const` and `title`)
25
+
-**UntitledMultiSelectEnumSchema**: A multi-select enum allowing multiple values to be selected
26
+
-**TitledMultiSelectEnumSchema**: A multi-select enum with display titles for each option
27
+
-**LegacyTitledEnumSchema** (deprecated): The legacy enum schema using `enumNames` for backward compatibility
28
+
22
29
The server can request a single input or multiple inputs at once.
23
30
To help distinguish multiple inputs, each input has a unique name.
0 commit comments