Forgejo MCP has 29 tools with consistent naming (verb_noun pattern: get_, list_, create_, update_, etc.) and descriptions present for all tools. However, critical gaps exist: most tools lack visible input parameter schemas in the provided source code, parameter descriptions are sparse or missing, and output schemas are undocumented. The server shows good intent (tool annotations present, write/read-only risk classification), but schema completeness and parameter documentation fall short of production standards. Average tool description length appears adequate (~100-150 chars inferred), but parameter-level documentation is largely absent.

• Add complete JSON Schema definitions for all 29 tools' input parameters. Include type, description, enum constraints, min/max bounds, and format specifications. Reference: https://arcade.dev/patterns/constrained-input
• Document output schemas for all tools. Specify field names, types, and which fields are required for downstream tool chaining (e.g., owner/repo IDs for follow-up calls). Reference: https://arcade.dev/patterns/response-shaper
• Add parameter descriptions to all tools lacking them. For each parameter, explain what it controls, valid values, and format (e.g., 'owner: Repository owner username (2-39 alphanumeric chars)'). Reference: https://arcade.dev/patterns/tool-description
• Implement error handling with recovery guidance. Return structured errors with error_type, message, and suggested_next_action. Example: 'Repository not found. Try list_repositories() to find available repos.' Reference: https://arcade.dev/patterns/recovery-guide
• Add confirmation/dry-run support for destructive operations (commit_changes, update_repository, migrate_repository). Implement a 'dry_run' parameter or separate 'preview_*' tools to let agents validate before executing. Reference: https://arcade.dev/patterns/confirmation-request