feat: add type-safe elicitation schema support (#465) (#466)

* feat: add type-safe elicitation schema support (#465)

Implement type-safe schema definitions for MCP elicitation requests,
replacing generic `JsonObject` with strongly-typed primitive schemas
per the [MCP 2025-06-18 specification](https://spec.modelcontextprotocol.io/specification/2025-06-18/server/elicitation/).

Features:
- Type-safe schema hierarchy (`StringSchema`, `NumberSchema`, `IntegerSchema`, `BooleanSchema`)
- Builder pattern with fluent API and 20+ convenience methods
- Build-time validation ensuring required fields exist in properties
- Private fields enforcing invariants through validated constructors
- Comprehensive validation support (range, length, format, enums)
- Typed property methods for cleaner schema construction

Benefits:
- Compile-time type safety prevents invalid schema construction
- 60-70% reduction in boilerplate through convenience methods
- Enforces MCP specification requirement for primitive-only properties
- Better IDE autocomplete and type inference
- Runtime validation catches schema errors early

Breaking changes:
- `CreateElicitationRequestParam.requested_schema` changed from `JsonObject` to `ElicitationSchema`
- `ElicitationSchemaBuilder::build()` now returns `Result` instead of direct value

Fixes #465

* fix: fix RMCP compliance

* feat: add conversion methods to ElicitationSchema

Add from_json_schema() and from_type() methods to ElicitationSchema
for easier type-to-schema conversion. This addresses feedback about
improving ergonomics when working with generated schemas.

Also make all struct fields public for better flexibility.

* chore: change `StringFormat` to enum

Author: ByteBaker

crates/rmcp/src/model.rs

@@ -2,6 +2,7 @@ use std::{borrow::Cow, sync::Arc};
 mod annotated;
 mod capabilities;
 mod content;
+mod elicitation_schema;
 mod extension;
 mod meta;
 mod prompt;
@@ -11,6 +12,7 @@ mod tool;
 pub use annotated::*;
 pub use capabilities::*;
 pub use content::*;
+pub use elicitation_schema::*;
 pub use extension::*;
 pub use meta::*;
 pub use prompt::*;
@@ -1377,7 +1379,21 @@ pub enum ElicitationAction {
 ///
 /// This structure contains everything needed to request interactive input from a user:
 /// - A human-readable message explaining what information is needed
-/// - A JSON schema defining the expected structure of the response
+/// - A type-safe schema defining the expected structure of the response
+///
+/// # Example
+///
+/// ```rust
+/// use rmcp::model::*;
+///
+/// let params = CreateElicitationRequestParam {
+///     message: "Please provide your email".to_string(),
+///     requested_schema: ElicitationSchema::builder()
+///         .required_email("email")
+///         .build()
+///         .unwrap(),
+/// };
+/// ```
 #[derive(Debug, Serialize, Deserialize, Clone, PartialEq)]
 #[serde(rename_all = "camelCase")]
 #[cfg_attr(feature = "schemars", derive(schemars::JsonSchema))]
@@ -1387,10 +1403,10 @@ pub struct CreateElicitationRequestParam {
     /// what information they need to provide.
     pub message: String,
 
-    /// JSON Schema defining the expected structure and validation rules for the user's response.
-    /// This allows clients to validate input and provide appropriate UI controls.
-    /// Must be a valid JSON Schema Draft 2020-12 object.
-    pub requested_schema: JsonObject,
+    /// Type-safe schema defining the expected structure and validation rules for the user's response.
+    /// This enforces the MCP 2025-06-18 specification that elicitation schemas must be objects
+    /// with primitive-typed properties.
+    pub requested_schema: ElicitationSchema,
 }
 
 /// The result returned by a client in response to an elicitation request.