This commit resolves critical parameter validation and type conversion issues
that were preventing tools from working correctly with MCP clients.
## Fixed Issues:
### Parameter Validation & Type Conversion
- Fixed Union[str, int] validation errors in ProcessTracingTools
- Added comprehensive boolean parameter handling (strings, ints, None)
- Resolved datetime import scoping in nested functions
- Fixed async/await requirements for all MCP tools
### Tools Fixed (Key Examples):
- process_tracing_process_monitor: Fixed duration parameter validation
- asciinema_*: All boolean parameters now handle "true"/"false" strings
- file_ops_*: Added 4 new directory management tools with safety checks
- utility_generate_documentation: Converted from NotImplementedError to async
- search_analysis_search_and_replace_batch: Fixed dry_run parameter blocking
- network_api_*: Fixed headers JSON conversion and api_mock_server
### New Features:
- Added comprehensive directory management tools (create, copy, move, remove)
- Safety checks now allow /tmp operations for testing
- All placeholder tools now return informative responses
### Documentation:
- Added TOOL_NAMES.md with complete list of all 71 tools
- Added TESTING_STRATEGY.md for FastMCP testing patterns
- Added comprehensive test suites for all fixes
All tools tested and verified working with proper parameter validation.
✅ COMPREHENSIVE SAFETY FRAMEWORK:
• Package-level safety notices with SACRED TRUST language
• Server-level LLM safety protocols with specific refusal scenarios
• Class-level safety reminders for AI assistants
• Tool-level destructive operation warnings (🔴 DESTRUCTIVE markers)
• Visual safety system: 🔴🛡️🚨 markers throughout codebase
• Emergency logging infrastructure with proper escalation
• Default-safe operations (dry_run=True for destructive tools)
🔒 DESTRUCTIVE OPERATION PROTECTIONS:
• bulk_rename: LLM safety instructions + dry_run default
• search_and_replace_batch: Comprehensive safety warnings
• All destructive tools require preview before execution
• Clear REFUSE scenarios for AI assistants
📚 COMPREHENSIVE DOCUMENTATION:
• SACRED_TRUST_SAFETY.md: Complete safety philosophy & implementation guide
• IMPLEMENTATION_COMPLETE.md: Project completion status
• EMERGENCY_LOGGING_COMPLETE.md: Logging infrastructure details
• UV_BUILD_GUIDE.md: Modern Python project setup
• Multiple implementation guides and status docs
🔧 PROJECT MODERNIZATION:
• Migrated from setup.py/requirements.txt to pyproject.toml + uv
• Updated dependency management with uv.lock
• Enhanced test suite with comprehensive coverage
• Added examples and demo scripts
✅ VALIDATION COMPLETE: All SACRED_TRUST_SAFETY.md requirements implemented
🎯 Sacred Trust Status: PROTECTED
🚨 User Safety: PARAMOUNT
🔐 System Integrity: PRESERVED
The human trusts AI assistants to be guardians of their system and data.
This framework ensures that trust is honored through comprehensive safety measures.
