Add required field for tool input schema for server #36
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
Close #35
This pull request refactors how tool schemas are defined and registered across several example servers and the core MCP server implementation. The main change is the transition from using raw schema property maps to dedicated
ToolInputSchemaandToolOutputSchemaobjects, improving type safety and clarity. Backwards compatibility is maintained for the old properties with deprecation notices.Core API and Schema Registration Changes
McpServer.toolmethod now acceptstoolInputSchemaandtoolOutputSchemaparameters instead of (or in addition to, for backwards compatibility) the previousinputSchemaPropertiesandoutputSchemaPropertiesmaps. The old parameters are marked as deprecated. (lib/src/server/mcp.dart)_RegisteredToolclass and related logic have been updated to store and useToolInputSchemaandToolOutputSchemainstead of raw property maps. (lib/src/server/mcp.dart) [1] [2] [3]Example Server Updates
server_stdio.dart,server_sse.dart,server_streamable_https.dart,weather.dart,server_iostream.dart) have been updated to use the newtoolInputSchemaparameter, replacinginputSchemaProperties. Where appropriate, required fields are now explicitly listed. [1] [2] [3] [4] [5] [6] [7] [8] [9]These changes modernize the schema registration approach, making it more robust and maintainable while preserving compatibility with existing code.