This server exposes 4 crowdfunding tools with mixed quality. Tool naming is verb-driven and clear (get_projects, search_projects, invest, create_project), following convention. Descriptions are present but generic and lack depth, they do not explain WHEN to use each tool, dependencies between them, or constraints. Input schemas are well-formed with proper types and required fields, but parameter descriptions are terse (5-20 chars) and fail to provide actionable guidance. Output schemas are not documented at all, LLMs cannot infer what fields are returned or how to chain tools. Error handling in the server code (mcp_server/server.py) validates inputs and returns McpError with context, which is good, but tool descriptions do not guide recovery. The invest and create_project tools modify state but their descriptions do not explicitly warn of irreversibility. Overall, this is a functional but below-average implementation, typical of community servers that focus on happy-path definitions and neglect production-grade documentation.

• Add output schema documentation to all tools. Example for get_projects: 'Returns an array of project objects, each with fields: id (string), title (string), description (string), funding_goal (number), current_funding (number), category (string, optional).'
• Expand parameter descriptions to 50 - 150 chars with format and constraint hints. Example for query in search_projects: 'Search term to match against project titles and descriptions. Accepts partial matches, case-insensitive. Minimum 1 character, maximum 256 characters.'
• Expand tool descriptions to clarify intent and differentiation. Example for get_projects: 'Retrieve all active crowdfunding projects with current funding status. Use this to explore available projects. For targeted search, use search_projects() instead. Returns paginated results (see pagination params).'
• Add explicit state-modification warnings to invest and create_project. Example: 'WARNING: This operation is irreversible and deducts funds immediately. No undo or dry-run available.'
• Add JSON Schema constraints: minimum: 0.01 for amount (cents), minimum: 1 for funding_goal, minLength: 1 and maxLength: 256 for title and query strings.
• Implement pagination on get_projects: add optional parameters limit (default 20, max 100) and offset (default 0), and return total_count and has_more in the response.
• Document that category in create_project is optional; update schema to reflect this if not already reflected.
• Add recovery guidance to error messages. Example: 'Investment failed: project not found. Use search_projects() to find the correct project ID.'

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

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