Skip to content

fix(schema): extract ElicitationCompleteNotificationParams to extend NotificationParams#2866

Open
clouatre wants to merge 1 commit into
modelcontextprotocol:mainfrom
clouatre:fix/elicitation-complete-notification-params
Open

fix(schema): extract ElicitationCompleteNotificationParams to extend NotificationParams#2866
clouatre wants to merge 1 commit into
modelcontextprotocol:mainfrom
clouatre:fix/elicitation-complete-notification-params

Conversation

@clouatre
Copy link
Copy Markdown
Contributor

@clouatre clouatre commented Jun 5, 2026

Summary

ElicitationCompleteNotification was the only notification in the schema whose params was an anonymous inline object. Every other notification (CancelledNotification, ProgressNotification, ResourceUpdatedNotification, LoggingMessageNotification, SubscriptionsAcknowledgedNotification) uses a named *NotificationParams interface that extends NotificationParams.

This extracts ElicitationCompleteNotificationParams extends NotificationParams and wires it into ElicitationCompleteNotification, restoring consistency and ensuring the universal _meta field is inherited.

Changes

  • schema/draft/schema.ts: add ElicitationCompleteNotificationParams interface before ElicitationCompleteNotification
  • schema/draft/schema.json: regenerated via npm run generate:schema
  • docs/specification/draft/schema.mdx: regenerated via npm run generate:schema

Testing

  • npm run check:schema passes clean (TypeScript, ESLint, Prettier, JSON validation, 127 examples)

Closes #2651

…NotificationParams

Signed-off-by: Hugues Clouâtre <hugues@linux.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ElicitationCompleteNotification: intentional omission of NotificationParams?

1 participant