hellyee defines 23 tools with consistent verb-noun naming (check_, get_, set_, create_, delete_, fire_, add_, replace_, quantize_). All tools have descriptions in Turkish, though many are terse (10-50 chars). Input schemas are present for all tools with proper type definitions (string, number, integer, boolean, array). However, parameter descriptions are minimal or missing context about constraints, ranges, and dependencies. Output schemas are not documented, tools return JSON strings but the structure is not specified. Error handling is absent from tool definitions. The server demonstrates good naming discipline and basic schema structure but lacks the depth needed for production-grade LLM interaction.

• Document output schemas for all tools. For get_song_status, specify: {tempo: number, is_playing: boolean, tracks: [{index: int, name: string, kind: 'midi'|'audio', ...}]}. For get_clip_notes, specify: {notes: [{pitch: int, start: float, duration: float, velocity: int}]}.
• Add explicit enum constraints to parameter descriptions. E.g., transport action: 'One of: start, stop, continue'. get_scale_notes scale: 'One of: major, minor, harmonic_minor, melodic_minor, dorian, phrygian, lydian, mixolydian, locrian, pentatonic_major, pentatonic_minor, blues, chromatic'.
• Add numeric bounds to all numeric parameters. E.g., set_tempo bpm: 'Tempo in BPM (20 - 300)'. set_mixer volume: '0.0 - 1.0 (0.85 ≈ 0 dB)'. quantize_clip strength: '0.0 - 1.0 (0.5 = half-strength, 0.6 - 0.8 recommended for recordings)'.
• Translate all descriptions to English and add recovery hints for error cases. E.g., set_tempo: 'If Ableton is not responding, call check_connection() first.' delete_track: 'This is irreversible. Confirm with the user before calling.'
• Implement a confirmation pattern for destructive operations. Add a dry_run parameter (boolean, default false) to delete_track, delete_clip, and clear_clip_notes. When dry_run=true, return what would be deleted without executing. When false, execute and return confirmation.