This is a teaching/demo repository ('mcp-for-beginners') with multiple example servers and significant quality issues. The codebase contains 17 tools spread across 5+ separate server files, with extensive duplication (add/subtract/multiply/divide appear 3+ times each), missing descriptions on critical tools, and no input schemas visible in most definitions. Tool naming is verb-first which is good (get_weather, calculate_sum), but composition is poor, many tools lack output documentation, error handling, and recovery guidance. The largest issue is SCHEMA VISIBILITY: only 2 tools show complete input schemas in the source (stdio_server.py tools have inline schema dicts). The server also uses STDIO transport exclusively in most examples, capping protocol readiness at 50.

• Consolidate duplicate math tools: replace 'add (number)', 'add (integer)' with a single polymorphic 'add' tool that accepts number type and documents both float and int handling.
• Add explicit output schemas to every tool. Document what get_weather returns: {location: string, temperature: float, conditions: string}. Document what forecast returns: {location, forecast: [{day, temperature, conditions}], total_days}.
• Expand descriptions to 50-200 chars. Instead of 'Gets current weather for a location.', write 'Get current weather conditions (temperature, conditions) for a specified location (city name or zip code). Use to answer user questions like "What is the weather in Boston?"'
• Add error handling examples. Document divide: 'Divides two numbers. Returns error if b=0; suggest reciprocal or factorization approach to user.'
• For FastMCP tools, ensure input schemas are generated and visible. FastMCP should auto-generate from Python type hints (a: int, b: int → {type: object, properties: {a: {type: integer}, b: {type: integer}}}); verify this is exported.
• Remove or rename 'help' tool. It is not a proper tool (returns static text, not useful for agents). Replace with 'list_tools' if needed, or omit entirely.
• Add natural-language parameter handling. Instead of requiring opaque IDs, let get_weather accept city names, zip codes, lat/lon tuples. Resolve internally.
• Document resource/prompt definitions if present. The repo mentions resources (greeting://{name}), but they lack description text. Add descriptions to all resources: 'Fetch a personalized greeting for a user by name.'

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

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