Skip to main content
Glama
aws-cost-mcp

aws-cost-mcp

EC2 rightsizing recommendations

get_rightsizing
Read-onlyIdempotent

Retrieve AWS EC2 rightsizing recommendations for instances to downsize or terminate, ordered by estimated monthly savings. Requires rightsizing recommendations enabled in Cost Explorer.

Instructions

EC2 instances AWS recommends to downsize or terminate, largest estimated monthly savings first. Needs rightsizing recommendations enabled in Cost Explorer preferences.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_rightsizing"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNomarkdown: compact table for reading. json: structured data.markdown
targetNoSAME_INSTANCE_FAMILY only suggests a smaller size of the same family (low risk). CROSS_INSTANCE_FAMILY may suggest a different family (bigger savings, needs testing).SAME_INSTANCE_FAMILY
benefitsConsideredNoAccount for existing Savings Plans / Reserved Instances when estimating savings.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds useful behavior beyond that: result ordering and the prerequisite configuration. It doesn't say what happens when the feature is disabled (empty result vs. error) and says nothing about volume or pagination.

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?

Two sentences, zero filler; the result set and ordering come first, and the prerequisite follows. Nothing could be removed without losing information.

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?

With no output schema, the description carries the burden of explaining returns, and it does so adequately (recommendation set, ordering). The main remaining gap is result volume or pagination behavior for accounts with many instances.

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

Parameters4/5

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

Schema description coverage is 100% and both enums carry detailed explanations, including the risk tradeoff between SAME_INSTANCE_FAMILY and CROSS_INSTANCE_FAMILY. The description adds no parameter meaning of its own, so baseline 3 applies.

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

Purpose4/5

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

States a specific resource (EC2 instances) and what the set contains (downsize-or-terminate recommendations), plus the ordering (largest estimated monthly savings first). It's unambiguous what the tool returns, though it doesn't explicitly contrast itself with siblings like get_cost_breakdown or get_anomalies.

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

Usage Guidelines3/5

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

Provides one important operational condition — rightsizing recommendations must be enabled in Cost Explorer preferences — which tells the agent when the call will come back empty. But there is no guidance on when to pick this over alternatives for cost analysis, so usage is only implied.

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