forge-mcp provides 24 tools with consistent naming (verb_noun pattern) and descriptions for all tools. However, parameter descriptions are minimal (often single phrases like 'Forge alias identifier'), and output schemas are not documented in the provided code. Input schemas are present but lack detail on constraints, enums, and validation rules. Error handling guidance is absent. The server demonstrates solid foundational structure but lacks the depth needed for production-grade LLM interaction.

• Document output schemas for all tools. For list_repositories, specify: {repositories: [{id: string, name: string, owner: string, url: string, description: string}], total: number}. For get_change_request, include all fields the LLM needs to decide next steps (status, author, reviewers, checks_passed).
• Add enum constraints to parameters. Change 'state' in list_change_requests to enum: ['open', 'closed', 'all']. Change 'event' in submit_change_request_review to enum: ['APPROVE', 'REQUEST_CHANGES', 'COMMENT']. Change 'merge_method' to enum: ['merge', 'squash', 'rebase'].
• Expand parameter descriptions with format and validation rules. E.g., 'owner: Repository owner username (2-39 alphanumeric chars, no spaces)' instead of 'Repository owner'. For 'ref' in read_repository_file, add 'Branch, tag, or commit SHA (40-char hex). Defaults to repository default branch.'
• Add error recovery guidance to tool descriptions. E.g., 'If repository not found, call list_repositories() to discover available repos. If change request not found, verify the index number with list_change_requests().'
• Implement confirmation for destructive operations. Add optional 'dry_run: boolean' parameter to commit_patch, rebase_branch, and close_change_request. Return a preview of changes and require explicit confirmation before executing.

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

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