MCP Tool Architect — Compare Workflow

Description: Evaluate multiple approaches or versions

When to Use

Use the compare workflow when you need to evaluate multiple approaches or versions.

Input Requirements

• MCP protocol specifications and tool definition schemas
• FCC service API definitions and capability inventories
• Prompt engineering templates and context management patterns
• Resource URI design standards and naming conventions

Process

1. Initialize — Set up the compare context for MCP Tool Architect
2. Execute — Perform the compare operation following MCP Tool Architect's style
3. Validate — Check output against quality gates
4. Handoff — Deliver results to downstream personas

Output

• MCP tool definition documents with JSON schemas
• Resource URI designs with naming convention documentation
• Prompt engineering patterns for tool discovery and usage
• MCP server configuration specifications

Quality Gates

• All tool definitions must conform to MCP specification
• Resource URIs must follow consistent naming conventions
• Tool descriptions must be unambiguous for AI agent interpretation
• No tool definitions without input/output schema validation
• Rate limiting and quota management required for all exposed tools