GCP Cost MCP Server with High-Level Pricing Tools

### What is the feature or problem you’d like to solve?

The existing repo https://github.com/nozomi-koborinai/gcp-cost-mcp-server gcp-cost MCP server provides excellent low-level SKU pricing lookups but lacks high-level abstractions needed for practical cloud migration and cost estimation workflows.

Current capabilities:

✅ Low-level SKU pricing lookups
✅ Service and SKU discovery
✅ Real-time pricing data
Missing capabilities:

❌ VM specification → Machine type mapping
❌ Architecture-level cost estimation
❌ Batch processing for multiple resources (e.g., RVTools files with 100s of VMs)
❌ Structured output formats (CSV, JSON for reporting)
❌ Cost optimization recommendations (commitment pricing, region comparison)
❌ Business-friendly explanations
Users must build complex wrapper layers to translate between user intent ("price a 4 vCPU, 16GB VM") and low-level SKU calls (find CPU SKU, memory SKU, storage SKU, then aggregate). This creates significant friction for common use cases like cloud migration cost estimation, RVTools file processing, multi-cloud cost comparison, and TCO analysis.

### Why do you need this feature?

This feature would solve critical problems in cloud migration and cost planning workflows:

Massive API Call Reduction: Current approach requires 4000+ API calls to process 500 VMs from RVTools. With batch pricing, this becomes 1 call—a 95% reduction.

Developer Productivity: Teams spend 80% of their time building wrapper code to translate between business requirements and low-level SKU lookups. High-level tools eliminate this overhead.

Real-World Testing Results: We tested 36 common pricing scenarios:

Current: Only 22% work directly, 39% require custom wrapper layers

### Example prompts, workflows, or additional information

"What's the monthly cost for a 4 vCPU, 16GB VM with 100GB standard disk in us-central1?"
"Estimate GCP costs for these 500 VMs from our RVTools export"
"Should we use committed use discounts for our n2-standard-4 instances?"
"Which region is cheapest for deploying a 4 vCPU, 16GB VM?"
"Estimate monthly cost for a 3-tier architecture: 3 web servers (2 vCPU, 8GB), 2 app servers (4 vCPU, 16GB), 1 Cloud SQL database (4 vCPU, 16GB, 500GB storage)"

Start by reviewing the linked gcp-cost-mcp-server and its existing low-level SKU pricing capabilities. Break the proposal into separately scoped tools for VM mapping, architecture estimates, batch processing, structured output, optimization, and explanations; done requires explicit acceptance criteria for each supported workflow.

Written by the indexing model from the issue text.