Skip to content

Commit ec14189

Browse files
authored
Merge pull request modelcontextprotocol#892 from LucaButBoring/chore/elicitation-schema-depth-limit
Clarify reasoning for limited elicitation schema
2 parents 3cbdc46 + 46fd161 commit ec14189

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/specification/draft/client/elicitation.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -198,7 +198,7 @@ sequenceDiagram
198198

199199
## Request Schema
200200

201-
The `requestedSchema` field allows servers to define the structure of the expected response using a restricted subset of JSON Schema. To simplify implementation for clients, elicitation schemas are limited to flat objects with primitive properties only:
201+
The `requestedSchema` field allows servers to define the structure of the expected response using a restricted subset of JSON Schema. To simplify client user experience, elicitation schemas are limited to flat objects with primitive properties only:
202202

203203
```json
204204
"requestedSchema": {
@@ -279,7 +279,7 @@ Clients can use this schema to:
279279
2. Validate user input before sending
280280
3. Provide better guidance to users
281281

282-
Note that complex nested structures, arrays of objects, and other advanced JSON Schema features are intentionally not supported to simplify client implementation.
282+
Note that complex nested structures, arrays of objects, and other advanced JSON Schema features are intentionally not supported to simplify client user experience.
283283

284284
## Response Actions
285285

0 commit comments

Comments
 (0)