Skip to main content
Glama
sebdroid

AWS Pricing MCP Server

by sebdroid

generate_cost_report

Read-only

Analyze AWS service costs by producing detailed reports that include unit pricing, calculation breakdowns, assumptions, and exclusions. Choose markdown or CSV.

Instructions

Generate a detailed cost analysis report based on pricing data for one or more AWS services.

This tool requires AWS pricing data and provides options for adding detailed cost information.

IMPORTANT REQUIREMENTS:

  • ALWAYS include detailed unit pricing information (e.g., "$0.0008 per 1K input tokens")

  • ALWAYS show calculation breakdowns (unit price × usage = total cost)

  • ALWAYS specify the pricing model (e.g., "ON DEMAND")

  • ALWAYS list all assumptions and exclusions explicitly

Output Format Options:

  • 'markdown' (default): Generates a well-formatted markdown report

  • 'csv': Generates a CSV format report with sections for service information, unit pricing, cost calculations, etc.

Example usage:

{
  // Required parameters
  "pricing_data": {
    // This should contain pricing data retrieved from get_pricing
    "status": "success",
    "service_name": "bedrock",
    "data": "... pricing information ...",
    "message": "Retrieved pricing for bedrock from AWS Pricing url"
  },
  "service_name": "Amazon Bedrock",

  // Core parameters (commonly used)
  "related_services": ["Lambda", "S3"],
  "pricing_model": "ON DEMAND",
  "assumptions": [
    "Standard ON DEMAND pricing model",
    "No caching or optimization applied",
    "Average request size of 4KB"
  ],
  "exclusions": [
    "Data transfer costs between regions",
    "Custom model training costs",
    "Development and maintenance costs"
  ],
  "output_file": "cost_analysis_report.md",  // or "cost_analysis_report.csv" for CSV format
  "format": "markdown",  // or "csv" for CSV format

  // Advanced parameter for complex scenarios
  "detailed_cost_data": {
    "services": {
      "Amazon Bedrock Foundation Models": {
        "usage": "Processing 1M input tokens and 500K output tokens with Claude 3.5 Haiku",
        "estimated_cost": "$80.00",
        "free_tier_info": "No free tier for Bedrock foundation models",
        "unit_pricing": {
          "input_tokens": "$0.0008 per 1K tokens",
          "output_tokens": "$0.0016 per 1K tokens"
        },
        "usage_quantities": {
          "input_tokens": "1,000,000 tokens",
          "output_tokens": "500,000 tokens"
        },
        "calculation_details": "$0.0008/1K × 1,000K input tokens + $0.0016/1K × 500K output tokens = $80.00"
      },
      "AWS Lambda": {
        "usage": "6,000 requests per month with 512 MB memory",
        "estimated_cost": "$0.38",
        "free_tier_info": "First 12 months: 1M requests/month free",
        "unit_pricing": {
          "requests": "$0.20 per 1M requests",
          "compute": "$0.0000166667 per GB-second"
        },
        "usage_quantities": {
          "requests": "6,000 requests",
          "compute": "6,000 requests × 1s × 0.5GB = 3,000 GB-seconds"
        },
        "calculation_details": "$0.20/1M × 0.006M requests + $0.0000166667 × 3,000 GB-seconds = $0.38"
      }
    }
  },

  // Recommendations parameter - can be provided directly or generated
  "recommendations": {
    "immediate": [
      "Optimize prompt engineering to reduce token usage for Claude 3.5 Haiku",
      "Configure Knowledge Base OCUs based on actual query patterns",
      "Implement response caching for common queries to reduce token usage"
    ],
    "best_practices": [
      "Monitor OCU utilization metrics and adjust capacity as needed",
      "Use prompt caching for repeated context across API calls",
      "Consider provisioned throughput for predictable workloads"
    ]
  }
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNoOutput format ("markdown" or "csv")markdown
exclusionsNoList of items excluded from cost analysis
assumptionsNoList of assumptions for cost analysis
output_fileNoPath to save the report file
pricing_dataYesRaw pricing data from AWS pricing tools
service_nameYesName of the AWS service
pricing_modelNoPricing model (e.g., "ON DEMAND", "Reserved")ON DEMAND
recommendationsNoDirect recommendations or guidance for generation
related_servicesNoList of related AWS services
detailed_cost_dataNoDetailed cost information for complex scenarios

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare readOnlyHint=true, and the description is consistent. It adds behavioral expectations: ALWAYS include unit pricing, calculation breakdowns, pricing model, assumptions, and exclusions. It also discloses output format options. This goes beyond the annotation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long, but front-loaded with a clear purpose and requirements, followed by structured sections and a comprehensive example. It earns its length for a 10-parameter tool, though the example is quite verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex tool with 10 parameters, nested objects, and an output schema, the description covers required input structure, output formats, report content requirements, and example usage. It omits return-value details, but the presence of an output schema reduces that burden.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description substantially enriches parameter semantics with a full JSON example showing the structure of pricing_data, detailed_cost_data, recommendations, and other parameters. It clarifies how pricing_data from get_pricing should be passed and the relationships between fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence uses a specific verb ('Generate') and resource ('cost analysis report') and clarifies the tool's scope (based on pricing data for one or more AWS services). This clearly distinguishes it from siblings that retrieve pricing or analyze projects.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description states the prerequisite ('This tool requires AWS pricing data') and provides an example showing pricing_data retrieved from get_pricing, implying a workflow. However, it doesn't explicitly name alternatives or state when not to use it, so it falls short of full guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sebdroid/aws-pricing-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server