Critical gaps across all tools. The primary tool 'bluesky_social_tool' is a portmanteau combining post/timeline/outbox operations into a single tool with 13 parameters, violating single-responsibility principle. Parameter descriptions are present but generic (e.g., 'Operation to perform'). No output schema is documented. Three helper tools (bluesky_help, bluesky_shutdown, show_outbox_card) have minimal descriptions and no visible input validation. The server uses fastmcp but tool definitions are incomplete, no evidence of enum constraints, error recovery guidance, or idempotent hints. Source code snippet cuts off mid-function, preventing full assessment of error handling.

• Split bluesky_social_tool into 6 focused tools: create_post (status_text, visibility, media_path, in_reply_to_id), list_timeline (timeline, limit, offset), list_notifications (limit, offset), enqueue_draft (status_text, visibility, media_path), approve_draft (outbox_id), publish_draft (outbox_id). Each tool has one clear responsibility.
• Add enum constraints to all operation-like parameters. E.g., 'operation' → enum: [outbox_list, outbox_enqueue, outbox_approve, outbox_publish, notifications, timeline]. Document valid values in parameter description.
• Document output schemas for all tools. E.g., bluesky_social_tool returns {success: bool, outbox_id?: int, message: string, items?: [{id, status, created_at, visibility}]}. Include field types and descriptions.
• Add dry_run support to all write operations (create_post, enqueue_draft, approve_draft, publish_draft). Default dry_run=true to prevent accidental publishes. Document in description: 'Set dry_run=false to execute; default is safe preview mode.'
• Expand tool descriptions to 80-150 chars. E.g., bluesky_help → 'Retrieve available operations and parameters for the Bluesky MCP server. Use this to discover supported actions before calling other tools.' bluesky_shutdown → 'Signal graceful shutdown of the MCP server. Requires explicit confirmation (dry_run=false). Host process handles actual termination.'

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry