Skip to content

Conversation

@somsubhro
Copy link

… Calculator workload estimate insights

Fixes

Summary

Changes

Added Workload estimate feature from Billing and Cost Management Pricing Calculator. AWS user guide reference: https://docs.aws.amazon.com/cost-management/latest/userguide/pricing-calculator.html. API reference: https://docs.aws.amazon.com/aws-cost-management/latest/APIReference/API_Operations_AWS_Billing_and_Cost_Management_Pricing_Calculator.html

Testing

  • Performed local testing
  • Ran uv run --frozen pytest --cov --cov-branch --cov-report=term-missing. Found no regression in coverage. Unit tests pass. New code files are at 99% code coverage
  • Ran pre-commit hook

User experience

You can now query and list workload estimates from your account, get insights into usage that you have modeled in workload estimates, and observe costs.

Checklist

If your change doesn't seem to apply, please leave them unchecked.

  • I have reviewed the contributing guidelines
  • I have performed a self-review of this change
  • Changes have been tested
  • Changes are documented

Is this a breaking change? N

RFC issue number:

Checklist:

  • Migration process documented
  • Implement warnings (if it can live side by side)

Acknowledgment

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the project license.

@codecov
Copy link

codecov bot commented Oct 9, 2025

Codecov Report

❌ Patch coverage is 98.55769% with 3 lines in your changes missing coverage. Please review.
✅ Project coverage is 89.50%. Comparing base (e82130f) to head (c2d5aa7).

Files with missing lines Patch % Lines
...t_mcp_server/tools/bcm_pricing_calculator_tools.py 98.54% 2 Missing and 1 partial ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1486      +/-   ##
==========================================
+ Coverage   89.46%   89.50%   +0.03%     
==========================================
  Files         724      725       +1     
  Lines       50966    51174     +208     
  Branches     8145     8193      +48     
==========================================
+ Hits        45596    45801     +205     
- Misses       3459     3461       +2     
- Partials     1911     1912       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@somsubhro
Copy link
Author

I have reviewed the missed code coverage lines and think those are expected.

)

# Handle pagination using shared utility
if max_pages:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NIT: Why does the LLM send this parameter? My suggestion is to actually push all request through paginate_aws_response. The max_pages should the be more of a configuration variable rather than dynamic input from the LLM.

chittev
chittev previously approved these changes Oct 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: To triage

Development

Successfully merging this pull request may close these issues.

5 participants