Skip to main content
Glama

aws_cloudwatch_get_metric_data

Retrieve time-series metric data from AWS CloudWatch for monitoring and analysis. Supports multiple metrics and math expressions in a single API call to track performance and resource utilization.

Instructions

Retrieve time-series metric data for one or more CloudWatch metrics. Supports multiple metrics and math expressions in a single call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
profileNoAWS profile name from ~/.aws/config (e.g., 'default', 'production')
regionNoAWS region override (e.g., 'us-east-1', 'sa-east-1')
metric_data_queriesYesMetric queries. Example: [{"Id": "m1", "MetricStat": {"Metric": {"Namespace": "AWS/EC2", "MetricName": "CPUUtilization", "Dimensions": [{"Name": "InstanceId", "Value": "i-xxx"}]}, "Period": 300, "Stat": "Average"}}]
start_timeYesStart time (ISO 8601, e.g., '2024-01-01T00:00:00Z')
end_timeYesEnd time (ISO 8601)
max_datapointsNoMaximum data points to return (default: 100)
Behavior2/5

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

No annotations provided, so description carries full burden. States read operation but omits critical AWS-specific behaviors: GetMetricData pricing model (per-metric cost), throttling limits, pagination behavior, or that it returns raw data points vs pre-aggregated statistics.

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 with zero waste. Front-loaded with core purpose (retrieve metric data), second sentence adds key differentiator (math expressions). Appropriate length for complexity level.

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?

Adequate for a read-only data retrieval tool with 100% schema coverage, but given AWS CloudWatch API complexity and lack of output schema, could benefit from notes on return format (timestamps, values) or cost warnings.

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 coverage is 100% with detailed examples. Description adds semantic value by noting 'math expressions' capability, hinting at the Expression field usage in metric_data_queries, but doesn't need to compensate for schema gaps.

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?

Specific verb 'Retrieve' with clear resource 'time-series metric data' and 'CloudWatch metrics'. The mention of 'math expressions' and 'multiple metrics' effectively distinguishes this from sibling aws_cloudwatch_get_metric_statistics (single metric statistics) and aws_cloudwatch_list_metrics (metadata only).

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?

Implies usage through capability listing (multiple metrics, math expressions), suggesting when to use this advanced API, but lacks explicit 'when to use vs alternatives' guidance or naming of sibling tool aws_cloudwatch_get_metric_statistics.

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/marcelobrake/aws-mcp'

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