This server has severe definition quality gaps. Tool names lack action verbs (handlePushEvent, handlePullRequestEvent violate verb_noun convention). Descriptions are present but generic and lack WHEN/WHY context. Critical issue: input schemas for 3 of 5 tools use bare 'object' type with no field definitions, these score 0 on schema. Parameters lack type constraints, enums, ranges, and validation guidance. No output schemas documented. Error handling is absent, functions log errors but return nothing to guide LLM recovery. The server implements webhook automation, not MCP tool patterns; tools are inferred from function names rather than explicitly registered with proper schemas.

• Rename tools to follow verb_noun pattern: 'create_pull_request', 'check_ci_status', 'merge_pull_request', 'auto_create_pr_on_feature_push', 'auto_merge_approved_pr'. This makes intent clear to LLMs.
• Add explicit JSON Schema definitions for all input parameters. For mergePullRequest, define the 'pr' object with required fields: pr_number (integer), head_sha (string), base_branch (string). For handlePushEvent, define event object with: ref (string), branch (string).
• Document output schemas for each tool. E.g., createPullRequest returns {pr_number: int, pr_url: string, created_at: ISO8601}. checkCIStatus returns {status: 'success'|'failure'|'pending', commit_sha: string}.
• Add error handling that returns structured errors with recovery guidance. E.g., 'PR creation failed: branch does not exist. Call list_branches() to see available branches.' instead of logging silently.
• Expand descriptions to 100-150 chars with WHEN/WHY context. E.g., 'Merges an approved pull request using squash strategy. Call this after checkCIStatus returns success and PR has approvals. Returns PR merge commit SHA.'