This is a Fastify plugin library for hosting MCP servers, not an MCP server itself. The single example tool 'greet' has minimal definition quality: no input schema documentation, trivial description, and no error handling guidance. The tool is inferred from code rather than explicitly registered with a visible schema definition. The example tools lack the rigor expected of production agent tools.

• Document the input schema explicitly. If 'greet' truly accepts no parameters, declare an empty JSON Schema with type 'object' and no properties, but add a note explaining the tool's purpose and expected output structure.
• Expand the tool description to 50-150 characters. Example: 'Returns a friendly greeting message. Use this tool to verify the server is running and responsive. Always returns a success response with a text message.'
• Add structured output documentation. Specify the exact fields returned (e.g., content array with text type), so LLMs know what to extract.
• Implement input validation and error handling. Even if inputs are empty, return clear error messages if something fails (e.g., 'Server error: Could not generate greeting. Try again.').
• If this is a demo library, upgrade the example tool to show best practices. Add a tool with at least one meaningful parameter (e.g., 'greet_with_name' accepting a 'name' string parameter) to demonstrate proper schema definition.

Inferred effective spec: 2026-07-28+.

• Relies on Stateful initialize / Mcp-Session-Id (removed; protocol is stateless) - make each request self-contained