Skip to main content
Glama
Sign In
AWS MCP Server

AWS MCP Server

by marcelobrake
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

aws_cloudfront_get_distribution

Retrieve complete configuration details for a CloudFront distribution using AWS MCP Server. Specify the distribution ID to access settings and properties.

Instructions

Get full configuration details for a CloudFront distribution.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "distribution_id": "<distribution_id>"
    },
    "name": "aws_cloudfront_get_distribution"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileNoAWS profile name from ~/.aws/config (e.g., 'default', 'production')
regionNoAWS region override (e.g., 'us-east-1', 'sa-east-1')
distribution_idYesCloudFront distribution ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. While 'Get' implies read-only, the description does not confirm idempotency or safety, disclose error conditions (e.g., invalid distribution ID), or describe the return structure despite no output schema being present.

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?

Single sentence of 7 words is efficient and front-loaded with the operative verb. No redundant content present, though extreme brevity contributes to gaps in behavioral and contextual disclosure.

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

Completeness2/5

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

Given AWS CloudFront complexity, lack of annotations, and absence of output schema, the description is insufficient. While it notes 'full configuration details', it fails to hint at key returned data (origins, cache behaviors, SSL settings) or AWS-specific behavioral constraints expected for this retrieval operation.

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%, establishing baseline 3. The description does not add parameter-specific guidance (e.g., explaining that distribution_id typically comes from list_distributions), but no additional compensation is required given complete schema documentation.

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?

Description uses specific verb 'Get' and resource 'CloudFront distribution'. The phrase 'full configuration details' implicitly distinguishes from sibling aws_cloudfront_list_distributions by implying detailed single-resource retrieval versus listing, though explicit sibling contrast is absent.

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

Usage Guidelines2/5

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

Provides no guidance on when to use this tool versus alternatives. Does not mention that aws_cloudfront_list_distributions should be used first to obtain the distribution_id, or specify scenarios requiring full configuration versus summary data.

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

Deploy Server

Other Tools