Database Tools Suite Consistency Review

Problem/Feature Description

DataFlow Systems has developed a suite of MCP tools for database operations, but the tools lack consistency. Different developers worked on different tools, resulting in:

• Inconsistent parameter naming (db_name, database, dbName)
• Different documentation structures
• Varying error formats
• No clear organization or grouping

The suite includes tools for:

1. Connection management - Connect, disconnect, test connections
2. Query execution - Run SQL queries, prepared statements
3. Schema operations - Create tables, alter schema, drop tables
4. Data migration - Import/export data, transform between formats
5. Backup/restore - Backup databases, restore from backups

The company wants to standardize these tools so they work well together and provide a cohesive experience for AI agents. Agents should be able to learn one tool and intuitively understand others in the suite.

Output Specification

Review the existing database tools and create a consistency improvement plan. Produce two files:

1. database_tools_standardized.json - A JSON file containing standardized definitions for at least 4 database tools, showing how they should be structured consistently.

2. consistency_guide.md - A markdown file explaining the consistency rules applied, covering:

   • Parameter naming conventions for common concepts
   • Standard documentation structure
   • Error format specification
   • Tool grouping and organization
   • Cross-tool references

The standardized tool definitions should demonstrate:

• Consistent parameter names for similar concepts (e.g., always use database_name not variations)
• Consistent parameter ordering (required before optional)
• Identical documentation structure across tools
• Uniform error formatting
• Logical tool grouping with prefixes
• Cross-references between related tools

The goal is to make the database tools feel like a unified suite rather than a collection of individual tools.