[jinglemansweep]

Implements three complementary approaches to help LLMs understand channel usage:

1. Enhanced Parameter Descriptions: Updated tool docstrings with detailed information about common channel names (e.g., "general", "public" map to channel 0)

2. Rich Return Context: Responses now include friendly channel names like "0 (General/Public)" instead of just the number, helping the LLM learn the channel ecosystem

3. Input Flexibility: The channel parameter now accepts both integers and string names ("general", "public", "main", "default" all map to 0), providing better UX and clearer intent

New helper functions:

• parse_channel_input(): Parses string names or numbers, with validation
• get_channel_display_name(): Returns friendly display names for channels

This addresses the common case where users say "send to general" or "send to public" without specifying channel 0.

[Copilot]

Pull request overview

This PR adds LLM-friendly enhancements to help AI assistants understand and use mesh radio channels more intuitively. The changes introduce three complementary approaches:

• Enhanced parameter descriptions with common channel name mappings
• Rich return context showing friendly channel names (e.g., "0 (General/Public)")
• Input flexibility accepting both integers (0-7) and string names ("general", "public", "main", "default")

Key changes include:

• New parse_channel_input() helper to handle both numeric and string channel inputs
• New get_channel_display_name() helper to provide user-friendly channel labels
• Updated meshcore_send_message() to accept string channel names in addition to numbers

Comments suppressed due to low confidence (2)

src/meshcore_mcp/server.py:10

• Import of 'asyncio' is not used.

import asyncio

src/meshcore_mcp/server.py:12

• Import of 'Dict' is not used.
  Import of 'Any' is not used.

from typing import Optional, List, Dict, Any

[Copilot]

The docstring lists "general", "public", "main" as examples but omits "default" which is also a valid channel name according to CHANNEL_NAME_MAP (line 59). The documentation should include all accepted channel names for completeness.