The NGA MCP server provides 4 tools for forum scraping with Chinese-language descriptions. All tools have descriptions and input schemas are present with type definitions. However, descriptions are verbose and include implementation details rather than LLM-optimized guidance. Parameter descriptions exist but lack constraint details (ranges, enums, format specifications). Output schemas are not formally documented. Error handling is basic (returns {success: false, error: str(e)}). Tool naming follows verb_noun pattern correctly. The server is functional but lacks production-grade polish in schema documentation and error guidance.

• Document output schema for each tool as a structured response specification in the tool description. Example: 'Returns: {success: bool, title: str, content: str, comments: [{author, text, timestamp}], error: str}'
• Add English descriptions alongside Chinese descriptions for global LLM compatibility
• Replace example URLs with formal format/pattern specifications: url parameter should have 'format: uri, pattern: ^https://bbs\.nga\.cn/(read|thread)\.php' constraints
• Convert parameter constraints into JSON Schema fields: 'topk' should declare 'minimum: 0, maximum: 1000' (or appropriate bounds) in the schema
• Implement structured error responses: return {success: false, error_code: 'INVALID_URL'|'NETWORK_ERROR'|'NOT_FOUND', message: 'User-friendly message', recovery_hint: 'Try X instead'} instead of bare exception strings
• Add error classification: document which errors are retryable (network timeouts) vs user-fixable (invalid URL format) vs fatal (cookies missing)
• For get_board_links, explicitly document: 'name parameter can be either a board name (returns topk fuzzy matches) OR a category name (returns all boards in category). Cannot mix both in one call.'
• Add example output structures to demonstrate the response format agents should expect from list_posts and crawl_post
• Consider pagination guidance for crawl_post and list_posts if results can exceed context window limits

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

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