Fix security for logging in server

[devcrocod]

• Fix debug logging in the createMessage method to include message count, maxTokens, temperature, and presence of a system prompt;
• Fix debug logging in the createElicitation method to show message length and schema property count
• Added trace logging

Motivation and Context

The full message was printed in the debug logs, which could contain confidential information

Breaking Changes

None

Types of changes

• 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

[Copilot]

Pull Request Overview

This PR refactors logging and type inference in the ServerSession class. The changes remove redundant explicit type parameters from request() calls and improve logging by separating debug-level summaries from trace-level detailed information.

Key Changes

• Removed explicit type parameters from request<T>() calls, relying on Kotlin's type inference
• Enhanced createMessage and createElicitation debug logs with structured summaries instead of full parameter dumps
• Added trace-level logging for full request details, following the existing logging pattern in the codebase

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[kpavlov]

Thank you, @devcrocod 👍🏻