Skip to main content
Glama
aws-samples

AWS DR Cost Estimator MCP Server

Official
by aws-samples

compare_dr_strategies

Compare disaster recovery costs across backup/restore, pilot light, warm standby, and active/active using live AWS Cost Explorer data to choose a cost-effective option.

Instructions

Compare DR cost across all four strategies using live Cost Explorer data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
top_nNoTop-N rollup size. Ignored when include_all_services is true.
regionNoOptional AWS region for the boto3 session. Cost Explorer is accessed via us-east-1.
profileNoOptional AWS named profile. Defaults to the boto3 credential chain.
months_backNoNumber of complete months of Cost Explorer history to average across (1-24).
tag_filtersNoOptional cost-allocation-tag scope mapping a tag key to accepted values, e.g. {"Project": ["checkout", "payments"], "Environment": ["prod"]}. Keys are ANDed; values within a key are ORed. Scopes the estimate to a tagged workload instead of the whole account/portfolio. Tag keys must be activated as cost allocation tags; untagged resources are excluded from the estimate.
linked_account_idsNoOptional list of 12-digit AWS account ids to restrict the query to.
include_all_servicesNoWhen true, skip the Top-N rollup.
warm_standby_capacityNoFraction of primary compute capacity kept warm in the DR region for the warm_standby strategy (0.1-1.0, default 0.5). Rescales fleet-shaped compute services (EC2, EBS, ECS, EMR) only; databases, storage, and control-plane fees are unaffected.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoPopulated only when ``success`` is False.
successYesTrue when the call succeeded. False indicates ``error`` is populated.
summaryNoPlain-text 2-4 sentence summary of the comparison. Empty string on error.
warningsNoNon-fatal warnings, for example when the summary generator fell back to its literal placeholder string.
top_servicesNoPortfolio-wide top-N services list, with current cost and per-strategy DR additional cost on each row.
confidence_summaryNoDollar-weighted confidence summary across the portfolio. Null on error.
per_account_totalsNoPer-account totals list with one row per account. For single-account inputs this list contains exactly one entry whose totals reconcile with the portfolio totals within rounding tolerance.
total_current_costNoSum of current_cost across all returned services, in USD.
per_strategy_totalsNoPortfolio-wide totals keyed by strategy id for the four supported strategies.
Behavior2/5

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

No annotations are provided, so the description must disclose behavior. It mentions using 'live Cost Explorer data' (source and recency) but does not state whether the operation is read-only, what permissions are needed, or any side effects. This is a significant gap for a tool that queries live data.

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

Conciseness5/5

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

The description is a single, concise sentence that front-loads the essential action and scope, with no wasted words.

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

Completeness3/5

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

Given the tool has 8 parameters and an output schema, the description is minimal but covers the core purpose. However, it lacks context about tool usage in workflows and behavioral details, making it thin for a tool of this complexity.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all 8 parameters thoroughly. The description itself adds no parameter-specific information, so it meets the baseline of 3.

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 description uses the specific verb 'Compare' with a clear resource ('DR cost across all four strategies') and distinguishes from sibling tools like list_dr_strategies and analyze_dr_strategy by focusing on comparing all strategies.

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 implies a clear use case (comparing DR costs) but does not explicitly mention when to use it versus alternatives such as analyzing a single strategy or listing strategies. It provides clear context but no exclusions.

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/aws-samples/sample-dr-cost-estimator-mcp'

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