Single tool 'entergram_get_me' has critical definition gaps. Input schema is empty object {} with no parameter descriptions. Tool description is minimal (34 chars, below 50-char baseline). No output schema documented. No error handling guidance. Tool naming follows verb_noun pattern but lacks context about what 'me' returns. This server exposes only a read-only authentication check, not a functional toolkit.

• Expand tool description to 100-200 chars: 'Retrieve the authenticated user's profile information including ID, email, name, and permissions. Call this after login to verify authentication succeeded and fetch user context for downstream operations.'
• Document output schema explicitly: { user_id: string, email: string, name: string, permissions: string[], authenticated_at: ISO8601 }
• Add error handling guidance: 'If authentication fails, prompt user to run `entergram-mcp login` first. If token expired, refresh via OAuth provider.'
• Consider expanding toolkit beyond authentication: add tools for workspace operations, message sending, or other Telegram/Entergram features to justify MCP server existence.
• Add parameter descriptions even for empty input schema (e.g., 'This tool accepts no parameters. It returns the currently authenticated user's profile.').