Skip to main content
Glama
aws-samples

AWS DR Cost Estimator MCP Server

Official
by aws-samples

analyze_dr_strategy

Estimates disaster recovery cost for a selected strategy using live Cost Explorer data. Returns average monthly cost based on strategy and filters.

Instructions

Analyze DR cost for a single strategy 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.
strategyYesDR strategy id. One of 'backup_restore', 'pilot_light', 'warm_standby', 'active_active'.
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.
totalsNoPortfolio totals across ``estimates``. Null on error.
successYesTrue when the call succeeded. False indicates ``error`` is populated.
summaryNoPlain-text 2-4 sentence summary of the analysis. Empty string on error.
strategyNoStrategy id the analysis was produced for. Null on error.
warningsNoNon-fatal warnings, for example when the summary generator fell back to its literal placeholder string.
estimatesNoPortfolio-level per-service rows. Includes the synthetic Top-N rollup row when the input contains more than ``top_n`` DR-eligible services and ``include_all_services`` is false.
per_accountNoPer-account sections with per-service detail. For single-account inputs contains exactly one entry whose totals reconcile with the portfolio totals within rounding tolerance.
top_n_rollupNoTransparent summary of services rolled into the 'Other Services' row. Null when no rollup occurred or when ``include_all_services`` is true.
strategy_labelNoHuman-readable strategy label. Null on error.
confidence_summaryNoDollar-weighted confidence summary across the portfolio. Null on error.
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the key behavioral trait of using 'live Cost Explorer data', implying real-time AWS access. However, it omits other useful details like whether the operation is read-only, any rate-limit considerations, or the nature of the output (covered by output schema).

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, front-loaded sentence that immediately states the action and scope. No wasted words, highly concise and effective.

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

Completeness4/5

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

The description is minimal but sufficient given a rich input schema and an existing output schema. It clearly communicates the purpose and data source. A slight gap is that it doesn't hint at what 'analyze' produces (e.g., cost breakdown, average), but the output schema covers return values, so completeness is good.

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%, and the parameter descriptions in the schema are detailed (e.g., tag_filters scoping, warm_standby_capacity rescaling). The tool description itself adds no additional parameter meaning beyond the schema, which is acceptable given high coverage.

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 clearly states the tool analyzes DR cost for a single strategy using live Cost Explorer data, with a specific verb ('Analyze') and resource ('DR cost for a single strategy'). It explicitly distinguishes from sibling tools like compare_dr_strategies by limiting to a single strategy.

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 phrase 'for a single strategy' provides clear usage context, implying this should be used when analyzing one strategy rather than comparing. However, it does not explicitly mention alternatives like compare_dr_strategies for multi-strategy comparison, though sibling names make the distinction apparent.

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