feat: add default value support to elicitation schemas (SEP-1034) by bug-ops · Pull Request #533 · modelcontextprotocol/rust-sdk

bug-ops · 2025-11-09T16:53:55Z

Summary

Implements modelcontextprotocol/modelcontextprotocol#1034 by adding optional default value support to StringSchema, NumberSchema, and EnumSchema in elicitation schemas.

Motivation

Resolves#521

Currently, users must manually enter information that could be pre-populated with sensible defaults, creating unnecessary friction in interactive tool workflows. For example, in an email reply tool, recipient and CC information from the email thread context should be automatically populated rather than requiring manual re-entry.

Changes

StringSchema: Added optional default: Option<Cow<'static, str>> field with with_default() builder method
NumberSchema: Added optional default: Option field with with_default() builder method
EnumSchema: Added optional default: Option field with with_default() builder method
Added comprehensive test coverage (8 new tests) for default value serialization, deserialization, and backward compatibility
Updated elicitation_stdio.rs example to demonstrate default values usage in a practical email reply scenario

Implementation Details:

Follows the existing BooleanSchema pattern for consistency
All defaults are optional (Option) for backward compatibility
Uses #[serde(skip_serializing_if = "Option::is_none")] to ensure old clients can safely ignore the new field
Type-safe: Rust's type system ensures defaults match their schema types

Example Usage

let schema = ElicitationSchema::builder().string_property("recipient", |s| {
s.format(StringFormat::Email).with_default("sender@example.com").description("Email recipient")}).number_property("confidence", |n| {
n.range(0.0,1.0).with_default(0.8).description("Reply confidence score")}).build()?;

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to change)
Documentation update

Checklist

I have read the MCP Documentation
My code follows the repository's style guidelines
New and existing tests pass locally
I have added appropriate error handling
I have added or updated documentation as needed

Implement optional default values for StringSchema, NumberSchema, and EnumSchema following the BooleanSchema pattern. This allows forms to be pre-populated with sensible defaults, improving user experience in elicitation workflows. Changes: - Add optional `default` field to StringSchema (Cow<'static, str>) - Add optional `default` field to NumberSchema (f64) - Add optional `default` field to EnumSchema (String) - Add `with_default()` builder methods to all three schemas - Add comprehensive tests for default value serialization and deserialization - Update elicitation example to demonstrate default values usage All defaults are optional (Option<T>) for backward compatibility and use skip_serializing_if to ensure old clients ignore the new field.

- Update server JSON RPC message schema with new default fields - Apply code formatting to elicitation example

Extract and display all fields from elicitation response including cc, body, and confidence in addition to previously shown recipient, subject, and priority fields.

Use default values from schema (sender@example.com, team@example.com, 0.8) instead of hardcoded fallback values when user doesn't provide input.

bug-ops · 2025-11-17T13:21:57Z

will be completed in pr #539

bug-ops · 2025-11-09T16:53:55Z

Summary

Implements modelcontextprotocol/modelcontextprotocol#1034 by adding optional default value support to StringSchema, NumberSchema, and EnumSchema in elicitation schemas.

Motivation

Resolves#521

Currently, users must manually enter information that could be pre-populated with sensible defaults, creating unnecessary friction in interactive tool workflows. For example, in an email reply tool, recipient and CC information from the email thread context should be automatically populated rather than requiring manual re-entry.

Changes

StringSchema: Added optional default: Option<Cow<'static, str>> field with with_default() builder method
NumberSchema: Added optional default: Option field with with_default() builder method
EnumSchema: Added optional default: Option field with with_default() builder method
Added comprehensive test coverage (8 new tests) for default value serialization, deserialization, and backward compatibility
Updated elicitation_stdio.rs example to demonstrate default values usage in a practical email reply scenario

Implementation Details:

Follows the existing BooleanSchema pattern for consistency
All defaults are optional (Option) for backward compatibility
Uses #[serde(skip_serializing_if = "Option::is_none")] to ensure old clients can safely ignore the new field
Type-safe: Rust's type system ensures defaults match their schema types

Example Usage

let schema = ElicitationSchema::builder().string_property("recipient", |s| {
s.format(StringFormat::Email).with_default("sender@example.com").description("Email recipient")}).number_property("confidence", |n| {
n.range(0.0,1.0).with_default(0.8).description("Reply confidence score")}).build()?;

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to change)
Documentation update

Checklist

I have read the MCP Documentation
My code follows the repository's style guidelines
New and existing tests pass locally
I have added appropriate error handling
I have added or updated documentation as needed

Implement optional default values for StringSchema, NumberSchema, and EnumSchema following the BooleanSchema pattern. This allows forms to be pre-populated with sensible defaults, improving user experience in elicitation workflows. Changes: - Add optional `default` field to StringSchema (Cow<'static, str>) - Add optional `default` field to NumberSchema (f64) - Add optional `default` field to EnumSchema (String) - Add `with_default()` builder methods to all three schemas - Add comprehensive tests for default value serialization and deserialization - Update elicitation example to demonstrate default values usage All defaults are optional (Option<T>) for backward compatibility and use skip_serializing_if to ensure old clients ignore the new field.

- Update server JSON RPC message schema with new default fields - Apply code formatting to elicitation example

Extract and display all fields from elicitation response including cc, body, and confidence in addition to previously shown recipient, subject, and priority fields.

Use default values from schema (sender@example.com, team@example.com, 0.8) instead of hardcoded fallback values when user doesn't provide input.

bug-ops · 2025-11-17T13:21:57Z

will be completed in pr #539

bug-ops · 2025-11-09T16:53:55Z

Summary

Implements modelcontextprotocol/modelcontextprotocol#1034 by adding optional default value support to StringSchema, NumberSchema, and EnumSchema in elicitation schemas.

Motivation

Resolves#521

Currently, users must manually enter information that could be pre-populated with sensible defaults, creating unnecessary friction in interactive tool workflows. For example, in an email reply tool, recipient and CC information from the email thread context should be automatically populated rather than requiring manual re-entry.

Changes

StringSchema: Added optional default: Option<Cow<'static, str>> field with with_default() builder method
NumberSchema: Added optional default: Option field with with_default() builder method
EnumSchema: Added optional default: Option field with with_default() builder method
Added comprehensive test coverage (8 new tests) for default value serialization, deserialization, and backward compatibility
Updated elicitation_stdio.rs example to demonstrate default values usage in a practical email reply scenario

Implementation Details:

Follows the existing BooleanSchema pattern for consistency
All defaults are optional (Option) for backward compatibility
Uses #[serde(skip_serializing_if = "Option::is_none")] to ensure old clients can safely ignore the new field
Type-safe: Rust's type system ensures defaults match their schema types

Example Usage

let schema = ElicitationSchema::builder().string_property("recipient", |s| {
s.format(StringFormat::Email).with_default("sender@example.com").description("Email recipient")}).number_property("confidence", |n| {
n.range(0.0,1.0).with_default(0.8).description("Reply confidence score")}).build()?;

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to change)
Documentation update

Checklist

I have read the MCP Documentation
My code follows the repository's style guidelines
New and existing tests pass locally
I have added appropriate error handling
I have added or updated documentation as needed

Implement optional default values for StringSchema, NumberSchema, and EnumSchema following the BooleanSchema pattern. This allows forms to be pre-populated with sensible defaults, improving user experience in elicitation workflows. Changes: - Add optional `default` field to StringSchema (Cow<'static, str>) - Add optional `default` field to NumberSchema (f64) - Add optional `default` field to EnumSchema (String) - Add `with_default()` builder methods to all three schemas - Add comprehensive tests for default value serialization and deserialization - Update elicitation example to demonstrate default values usage All defaults are optional (Option<T>) for backward compatibility and use skip_serializing_if to ensure old clients ignore the new field.

- Update server JSON RPC message schema with new default fields - Apply code formatting to elicitation example

Extract and display all fields from elicitation response including cc, body, and confidence in addition to previously shown recipient, subject, and priority fields.

Use default values from schema (sender@example.com, team@example.com, 0.8) instead of hardcoded fallback values when user doesn't provide input.

bug-ops · 2025-11-17T13:21:57Z

will be completed in pr #539

bug-ops · 2025-11-09T16:53:55Z

Summary

Implements modelcontextprotocol/modelcontextprotocol#1034 by adding optional default value support to StringSchema, NumberSchema, and EnumSchema in elicitation schemas.

Motivation

Resolves#521

Currently, users must manually enter information that could be pre-populated with sensible defaults, creating unnecessary friction in interactive tool workflows. For example, in an email reply tool, recipient and CC information from the email thread context should be automatically populated rather than requiring manual re-entry.

Changes

StringSchema: Added optional default: Option<Cow<'static, str>> field with with_default() builder method
NumberSchema: Added optional default: Option field with with_default() builder method
EnumSchema: Added optional default: Option field with with_default() builder method
Added comprehensive test coverage (8 new tests) for default value serialization, deserialization, and backward compatibility
Updated elicitation_stdio.rs example to demonstrate default values usage in a practical email reply scenario

Implementation Details:

Follows the existing BooleanSchema pattern for consistency
All defaults are optional (Option) for backward compatibility
Uses #[serde(skip_serializing_if = "Option::is_none")] to ensure old clients can safely ignore the new field
Type-safe: Rust's type system ensures defaults match their schema types

Example Usage

let schema = ElicitationSchema::builder().string_property("recipient", |s| {
s.format(StringFormat::Email).with_default("sender@example.com").description("Email recipient")}).number_property("confidence", |n| {
n.range(0.0,1.0).with_default(0.8).description("Reply confidence score")}).build()?;

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to change)
Documentation update

Checklist

I have read the MCP Documentation
My code follows the repository's style guidelines
New and existing tests pass locally
I have added appropriate error handling
I have added or updated documentation as needed

Implement optional default values for StringSchema, NumberSchema, and EnumSchema following the BooleanSchema pattern. This allows forms to be pre-populated with sensible defaults, improving user experience in elicitation workflows. Changes: - Add optional `default` field to StringSchema (Cow<'static, str>) - Add optional `default` field to NumberSchema (f64) - Add optional `default` field to EnumSchema (String) - Add `with_default()` builder methods to all three schemas - Add comprehensive tests for default value serialization and deserialization - Update elicitation example to demonstrate default values usage All defaults are optional (Option<T>) for backward compatibility and use skip_serializing_if to ensure old clients ignore the new field.

- Update server JSON RPC message schema with new default fields - Apply code formatting to elicitation example

Extract and display all fields from elicitation response including cc, body, and confidence in addition to previously shown recipient, subject, and priority fields.

Use default values from schema (sender@example.com, team@example.com, 0.8) instead of hardcoded fallback values when user doesn't provide input.

bug-ops · 2025-11-17T13:21:57Z

will be completed in pr #539

bug-ops · 2025-11-09T16:53:55Z

Summary

Implements modelcontextprotocol/modelcontextprotocol#1034 by adding optional default value support to StringSchema, NumberSchema, and EnumSchema in elicitation schemas.

Motivation

Resolves#521

Currently, users must manually enter information that could be pre-populated with sensible defaults, creating unnecessary friction in interactive tool workflows. For example, in an email reply tool, recipient and CC information from the email thread context should be automatically populated rather than requiring manual re-entry.

Changes

StringSchema: Added optional default: Option<Cow<'static, str>> field with with_default() builder method
NumberSchema: Added optional default: Option field with with_default() builder method
EnumSchema: Added optional default: Option field with with_default() builder method
Added comprehensive test coverage (8 new tests) for default value serialization, deserialization, and backward compatibility
Updated elicitation_stdio.rs example to demonstrate default values usage in a practical email reply scenario

Implementation Details:

Follows the existing BooleanSchema pattern for consistency
All defaults are optional (Option) for backward compatibility
Uses #[serde(skip_serializing_if = "Option::is_none")] to ensure old clients can safely ignore the new field
Type-safe: Rust's type system ensures defaults match their schema types

Example Usage

let schema = ElicitationSchema::builder().string_property("recipient", |s| {
s.format(StringFormat::Email).with_default("sender@example.com").description("Email recipient")}).number_property("confidence", |n| {
n.range(0.0,1.0).with_default(0.8).description("Reply confidence score")}).build()?;

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to change)
Documentation update

Checklist

I have read the MCP Documentation
My code follows the repository's style guidelines
New and existing tests pass locally
I have added appropriate error handling
I have added or updated documentation as needed

Implement optional default values for StringSchema, NumberSchema, and EnumSchema following the BooleanSchema pattern. This allows forms to be pre-populated with sensible defaults, improving user experience in elicitation workflows. Changes: - Add optional `default` field to StringSchema (Cow<'static, str>) - Add optional `default` field to NumberSchema (f64) - Add optional `default` field to EnumSchema (String) - Add `with_default()` builder methods to all three schemas - Add comprehensive tests for default value serialization and deserialization - Update elicitation example to demonstrate default values usage All defaults are optional (Option<T>) for backward compatibility and use skip_serializing_if to ensure old clients ignore the new field.

- Update server JSON RPC message schema with new default fields - Apply code formatting to elicitation example

Extract and display all fields from elicitation response including cc, body, and confidence in addition to previously shown recipient, subject, and priority fields.

Use default values from schema (sender@example.com, team@example.com, 0.8) instead of hardcoded fallback values when user doesn't provide input.

bug-ops · 2025-11-17T13:21:57Z

will be completed in pr #539

bug-ops · 2025-11-09T16:53:55Z

Summary

Implements modelcontextprotocol/modelcontextprotocol#1034 by adding optional default value support to StringSchema, NumberSchema, and EnumSchema in elicitation schemas.

Motivation

Resolves#521

Currently, users must manually enter information that could be pre-populated with sensible defaults, creating unnecessary friction in interactive tool workflows. For example, in an email reply tool, recipient and CC information from the email thread context should be automatically populated rather than requiring manual re-entry.

Changes

StringSchema: Added optional default: Option<Cow<'static, str>> field with with_default() builder method
NumberSchema: Added optional default: Option field with with_default() builder method
EnumSchema: Added optional default: Option field with with_default() builder method
Added comprehensive test coverage (8 new tests) for default value serialization, deserialization, and backward compatibility
Updated elicitation_stdio.rs example to demonstrate default values usage in a practical email reply scenario

Implementation Details:

Follows the existing BooleanSchema pattern for consistency
All defaults are optional (Option) for backward compatibility
Uses #[serde(skip_serializing_if = "Option::is_none")] to ensure old clients can safely ignore the new field
Type-safe: Rust's type system ensures defaults match their schema types

Example Usage

let schema = ElicitationSchema::builder().string_property("recipient", |s| {
s.format(StringFormat::Email).with_default("sender@example.com").description("Email recipient")}).number_property("confidence", |n| {
n.range(0.0,1.0).with_default(0.8).description("Reply confidence score")}).build()?;

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to change)
Documentation update

Checklist

I have read the MCP Documentation
My code follows the repository's style guidelines
New and existing tests pass locally
I have added appropriate error handling
I have added or updated documentation as needed

Implement optional default values for StringSchema, NumberSchema, and EnumSchema following the BooleanSchema pattern. This allows forms to be pre-populated with sensible defaults, improving user experience in elicitation workflows. Changes: - Add optional `default` field to StringSchema (Cow<'static, str>) - Add optional `default` field to NumberSchema (f64) - Add optional `default` field to EnumSchema (String) - Add `with_default()` builder methods to all three schemas - Add comprehensive tests for default value serialization and deserialization - Update elicitation example to demonstrate default values usage All defaults are optional (Option<T>) for backward compatibility and use skip_serializing_if to ensure old clients ignore the new field.

- Update server JSON RPC message schema with new default fields - Apply code formatting to elicitation example

Extract and display all fields from elicitation response including cc, body, and confidence in addition to previously shown recipient, subject, and priority fields.

Use default values from schema (sender@example.com, team@example.com, 0.8) instead of hardcoded fallback values when user doesn't provide input.

bug-ops · 2025-11-17T13:21:57Z

will be completed in pr #539

bug-ops · 2025-11-09T16:53:55Z

Summary

Implements modelcontextprotocol/modelcontextprotocol#1034 by adding optional default value support to StringSchema, NumberSchema, and EnumSchema in elicitation schemas.

Motivation

Resolves#521

Currently, users must manually enter information that could be pre-populated with sensible defaults, creating unnecessary friction in interactive tool workflows. For example, in an email reply tool, recipient and CC information from the email thread context should be automatically populated rather than requiring manual re-entry.

Changes

StringSchema: Added optional default: Option<Cow<'static, str>> field with with_default() builder method
NumberSchema: Added optional default: Option field with with_default() builder method
EnumSchema: Added optional default: Option field with with_default() builder method
Added comprehensive test coverage (8 new tests) for default value serialization, deserialization, and backward compatibility
Updated elicitation_stdio.rs example to demonstrate default values usage in a practical email reply scenario

Implementation Details:

Follows the existing BooleanSchema pattern for consistency
All defaults are optional (Option) for backward compatibility
Uses #[serde(skip_serializing_if = "Option::is_none")] to ensure old clients can safely ignore the new field
Type-safe: Rust's type system ensures defaults match their schema types

Example Usage

let schema = ElicitationSchema::builder().string_property("recipient", |s| {
s.format(StringFormat::Email).with_default("sender@example.com").description("Email recipient")}).number_property("confidence", |n| {
n.range(0.0,1.0).with_default(0.8).description("Reply confidence score")}).build()?;

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to change)
Documentation update

Checklist

I have read the MCP Documentation
My code follows the repository's style guidelines
New and existing tests pass locally
I have added appropriate error handling
I have added or updated documentation as needed

Implement optional default values for StringSchema, NumberSchema, and EnumSchema following the BooleanSchema pattern. This allows forms to be pre-populated with sensible defaults, improving user experience in elicitation workflows. Changes: - Add optional `default` field to StringSchema (Cow<'static, str>) - Add optional `default` field to NumberSchema (f64) - Add optional `default` field to EnumSchema (String) - Add `with_default()` builder methods to all three schemas - Add comprehensive tests for default value serialization and deserialization - Update elicitation example to demonstrate default values usage All defaults are optional (Option<T>) for backward compatibility and use skip_serializing_if to ensure old clients ignore the new field.

- Update server JSON RPC message schema with new default fields - Apply code formatting to elicitation example

Extract and display all fields from elicitation response including cc, body, and confidence in addition to previously shown recipient, subject, and priority fields.

Use default values from schema (sender@example.com, team@example.com, 0.8) instead of hardcoded fallback values when user doesn't provide input.

bug-ops · 2025-11-17T13:21:57Z

will be completed in pr #539

bug-ops · 2025-11-09T16:53:55Z

Summary

Implements modelcontextprotocol/modelcontextprotocol#1034 by adding optional default value support to StringSchema, NumberSchema, and EnumSchema in elicitation schemas.

Motivation

Resolves#521

Currently, users must manually enter information that could be pre-populated with sensible defaults, creating unnecessary friction in interactive tool workflows. For example, in an email reply tool, recipient and CC information from the email thread context should be automatically populated rather than requiring manual re-entry.

Changes

StringSchema: Added optional default: Option<Cow<'static, str>> field with with_default() builder method
NumberSchema: Added optional default: Option field with with_default() builder method
EnumSchema: Added optional default: Option field with with_default() builder method
Added comprehensive test coverage (8 new tests) for default value serialization, deserialization, and backward compatibility
Updated elicitation_stdio.rs example to demonstrate default values usage in a practical email reply scenario

Implementation Details:

Follows the existing BooleanSchema pattern for consistency
All defaults are optional (Option) for backward compatibility
Uses #[serde(skip_serializing_if = "Option::is_none")] to ensure old clients can safely ignore the new field
Type-safe: Rust's type system ensures defaults match their schema types

Example Usage

let schema = ElicitationSchema::builder().string_property("recipient", |s| {
s.format(StringFormat::Email).with_default("sender@example.com").description("Email recipient")}).number_property("confidence", |n| {
n.range(0.0,1.0).with_default(0.8).description("Reply confidence score")}).build()?;

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to change)
Documentation update

Checklist

I have read the MCP Documentation
My code follows the repository's style guidelines
New and existing tests pass locally
I have added appropriate error handling
I have added or updated documentation as needed

Implement optional default values for StringSchema, NumberSchema, and EnumSchema following the BooleanSchema pattern. This allows forms to be pre-populated with sensible defaults, improving user experience in elicitation workflows. Changes: - Add optional `default` field to StringSchema (Cow<'static, str>) - Add optional `default` field to NumberSchema (f64) - Add optional `default` field to EnumSchema (String) - Add `with_default()` builder methods to all three schemas - Add comprehensive tests for default value serialization and deserialization - Update elicitation example to demonstrate default values usage All defaults are optional (Option<T>) for backward compatibility and use skip_serializing_if to ensure old clients ignore the new field.

- Update server JSON RPC message schema with new default fields - Apply code formatting to elicitation example

Extract and display all fields from elicitation response including cc, body, and confidence in addition to previously shown recipient, subject, and priority fields.

Use default values from schema (sender@example.com, team@example.com, 0.8) instead of hardcoded fallback values when user doesn't provide input.

bug-ops · 2025-11-17T13:21:57Z

will be completed in pr #539

github-actionsBot added T-core Core library changes T-examples Example code changes T-model Model/data structure changes labels Nov 9, 2025

chore: update JSON schema and format code
f9d9039
- Update server JSON RPC message schema with new default fields - Apply code formatting to elicitation example

github-actionsBot added T-test Testing related changes T-config Configuration file changes labels Nov 9, 2025

This comment was marked as outdated.
Sign in to view

feat(examples): display all elicitation form fields in email reply tool
eff2d45
Extract and display all fields from elicitation response including cc, body, and confidence in addition to previously shown recipient, subject, and priority fields.

bug-ops marked this pull request as ready for review November 14, 2025 13:03

fix(examples): use schema default values as fallback in elicitation
22da84c
Use default values from schema (sender@example.com, team@example.com, 0.8) instead of hardcoded fallback values when user doesn't provide input.

bug-ops marked this pull request as draft November 15, 2025 14:09

bug-ops closed this Nov 17, 2025

bug-ops deleted the feat/sep-1034-default-values branch November 17, 2025 13:22

github-actionsBot added T-core Core library changes T-examples Example code changes T-model Model/data structure changes labels Nov 9, 2025

chore: update JSON schema and format code
f9d9039
- Update server JSON RPC message schema with new default fields - Apply code formatting to elicitation example

github-actionsBot added T-test Testing related changes T-config Configuration file changes labels Nov 9, 2025

This comment was marked as outdated.
Sign in to view

feat(examples): display all elicitation form fields in email reply tool
eff2d45
Extract and display all fields from elicitation response including cc, body, and confidence in addition to previously shown recipient, subject, and priority fields.

bug-ops marked this pull request as ready for review November 14, 2025 13:03

fix(examples): use schema default values as fallback in elicitation
22da84c
Use default values from schema (sender@example.com, team@example.com, 0.8) instead of hardcoded fallback values when user doesn't provide input.

bug-ops marked this pull request as draft November 15, 2025 14:09

bug-ops closed this Nov 17, 2025

bug-ops deleted the feat/sep-1034-default-values branch November 17, 2025 13:22

github-actionsBot added T-core Core library changes T-examples Example code changes T-model Model/data structure changes labels Nov 9, 2025

chore: update JSON schema and format code
f9d9039
- Update server JSON RPC message schema with new default fields - Apply code formatting to elicitation example

github-actionsBot added T-test Testing related changes T-config Configuration file changes labels Nov 9, 2025

This comment was marked as outdated.
Sign in to view

feat(examples): display all elicitation form fields in email reply tool
eff2d45
Extract and display all fields from elicitation response including cc, body, and confidence in addition to previously shown recipient, subject, and priority fields.

bug-ops marked this pull request as ready for review November 14, 2025 13:03

fix(examples): use schema default values as fallback in elicitation
22da84c
Use default values from schema (sender@example.com, team@example.com, 0.8) instead of hardcoded fallback values when user doesn't provide input.

bug-ops marked this pull request as draft November 15, 2025 14:09

bug-ops closed this Nov 17, 2025

bug-ops deleted the feat/sep-1034-default-values branch November 17, 2025 13:22

github-actionsBot added T-core Core library changes T-examples Example code changes T-model Model/data structure changes labels Nov 9, 2025

chore: update JSON schema and format code
f9d9039
- Update server JSON RPC message schema with new default fields - Apply code formatting to elicitation example

github-actionsBot added T-test Testing related changes T-config Configuration file changes labels Nov 9, 2025

This comment was marked as outdated.
Sign in to view

feat(examples): display all elicitation form fields in email reply tool
eff2d45
Extract and display all fields from elicitation response including cc, body, and confidence in addition to previously shown recipient, subject, and priority fields.

bug-ops marked this pull request as ready for review November 14, 2025 13:03

fix(examples): use schema default values as fallback in elicitation
22da84c
Use default values from schema (sender@example.com, team@example.com, 0.8) instead of hardcoded fallback values when user doesn't provide input.

bug-ops marked this pull request as draft November 15, 2025 14:09

bug-ops closed this Nov 17, 2025

bug-ops deleted the feat/sep-1034-default-values branch November 17, 2025 13:22

github-actionsBot added T-core Core library changes T-examples Example code changes T-model Model/data structure changes labels Nov 9, 2025

chore: update JSON schema and format code
f9d9039
- Update server JSON RPC message schema with new default fields - Apply code formatting to elicitation example

github-actionsBot added T-test Testing related changes T-config Configuration file changes labels Nov 9, 2025

This comment was marked as outdated.
Sign in to view

feat(examples): display all elicitation form fields in email reply tool
eff2d45
Extract and display all fields from elicitation response including cc, body, and confidence in addition to previously shown recipient, subject, and priority fields.

bug-ops marked this pull request as ready for review November 14, 2025 13:03

fix(examples): use schema default values as fallback in elicitation
22da84c
Use default values from schema (sender@example.com, team@example.com, 0.8) instead of hardcoded fallback values when user doesn't provide input.

bug-ops marked this pull request as draft November 15, 2025 14:09

bug-ops closed this Nov 17, 2025

bug-ops deleted the feat/sep-1034-default-values branch November 17, 2025 13:22

github-actionsBot added T-core Core library changes T-examples Example code changes T-model Model/data structure changes labels Nov 9, 2025

chore: update JSON schema and format code
f9d9039
- Update server JSON RPC message schema with new default fields - Apply code formatting to elicitation example

github-actionsBot added T-test Testing related changes T-config Configuration file changes labels Nov 9, 2025

This comment was marked as outdated.
Sign in to view

feat(examples): display all elicitation form fields in email reply tool
eff2d45
Extract and display all fields from elicitation response including cc, body, and confidence in addition to previously shown recipient, subject, and priority fields.

bug-ops marked this pull request as ready for review November 14, 2025 13:03

fix(examples): use schema default values as fallback in elicitation
22da84c
Use default values from schema (sender@example.com, team@example.com, 0.8) instead of hardcoded fallback values when user doesn't provide input.

bug-ops marked this pull request as draft November 15, 2025 14:09

bug-ops closed this Nov 17, 2025

bug-ops deleted the feat/sep-1034-default-values branch November 17, 2025 13:22

github-actionsBot added T-core Core library changes T-examples Example code changes T-model Model/data structure changes labels Nov 9, 2025

chore: update JSON schema and format code
f9d9039
- Update server JSON RPC message schema with new default fields - Apply code formatting to elicitation example

github-actionsBot added T-test Testing related changes T-config Configuration file changes labels Nov 9, 2025

This comment was marked as outdated.
Sign in to view

feat(examples): display all elicitation form fields in email reply tool
eff2d45
Extract and display all fields from elicitation response including cc, body, and confidence in addition to previously shown recipient, subject, and priority fields.

bug-ops marked this pull request as ready for review November 14, 2025 13:03

fix(examples): use schema default values as fallback in elicitation
22da84c
Use default values from schema (sender@example.com, team@example.com, 0.8) instead of hardcoded fallback values when user doesn't provide input.

bug-ops marked this pull request as draft November 15, 2025 14:09

bug-ops closed this Nov 17, 2025

bug-ops deleted the feat/sep-1034-default-values branch November 17, 2025 13:22

github-actionsBot added T-core Core library changes T-examples Example code changes T-model Model/data structure changes labels Nov 9, 2025

chore: update JSON schema and format code
f9d9039
- Update server JSON RPC message schema with new default fields - Apply code formatting to elicitation example

github-actionsBot added T-test Testing related changes T-config Configuration file changes labels Nov 9, 2025

This comment was marked as outdated.
Sign in to view

feat(examples): display all elicitation form fields in email reply tool
eff2d45
Extract and display all fields from elicitation response including cc, body, and confidence in addition to previously shown recipient, subject, and priority fields.

bug-ops marked this pull request as ready for review November 14, 2025 13:03

fix(examples): use schema default values as fallback in elicitation
22da84c
Use default values from schema (sender@example.com, team@example.com, 0.8) instead of hardcoded fallback values when user doesn't provide input.

bug-ops marked this pull request as draft November 15, 2025 14:09

bug-ops closed this Nov 17, 2025

bug-ops deleted the feat/sep-1034-default-values branch November 17, 2025 13:22

Uh oh!

Conversation

bug-ops commented Nov 9, 2025

Summary

Motivation

Changes

Implementation Details:

Example Usage

Checklist

Uh oh!

This comment was marked as outdated.

bug-ops commented Nov 17, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

bug-ops commented Nov 9, 2025

Summary

Motivation

Changes

Implementation Details:

Example Usage

Checklist

Uh oh!

This comment was marked as outdated.

bug-ops commented Nov 17, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

bug-ops commented Nov 9, 2025

Summary

Motivation

Changes

Implementation Details:

Example Usage

Checklist

Uh oh!

This comment was marked as outdated.

bug-ops commented Nov 17, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

bug-ops commented Nov 9, 2025

Summary

Motivation

Changes

Implementation Details:

Example Usage

Checklist

Uh oh!

This comment was marked as outdated.

bug-ops commented Nov 17, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects