Skip to main content
Glama
YawLabs

@yawlabs/aws-mcp

Official
by YawLabs

aws_call

Execute any AWS API operation by specifying a kebab-case service and operation, with parameters as a JSON object. Returns parsed JSON output.

Instructions

Run an arbitrary AWS API operation via the aws CLI. Use kebab-case service and operation names as in aws help (service='s3api', operation='list-buckets'). Pass params as a JSON object using the AWS API's PascalCase keys (e.g. {Bucket: 'foo'}); they go through --cli-input-json. Session profile/region (from aws_session_set) are used by default; override per-call when needed. For high-level wrappers like 'aws s3 cp' or 'aws ec2 wait', use your shell — this tool targets the low-level API. Returns parsed JSON output by default, plus the literal command that was run.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
serviceYesAWS service name in kebab-case: 's3api', 'ec2', 'iam', 'lambda', 'dynamodb', 'logs', 'sts', 'cloudformation', etc.
operationYesOperation name in kebab-case: 'list-buckets', 'describe-instances', 'get-caller-identity', 'put-object'.
paramsNoOperation parameters as a JSON object (AWS API schema, PascalCase keys). E.g. {Bucket: 'foo', Key: 'bar'}.
queryNoJMESPath expression to extract a subset of the response (passed as --query). E.g. 'Buckets[].Name', 'Reservations[].Instances[].{Id:InstanceId,State:State.Name}'. Dramatically reduces output size; reach for this whenever you only need a few fields.
profileNoOverride session profile for this call.
regionNoOverride session region for this call.
outputFormatNoOutput format. Default 'json' (parsed into structured data when possible).
timeoutMsNoTimeout in milliseconds. Default 60000 (60s). Raise for slow ops; lower to fail fast.
Behavior4/5

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

Annotations indicate possible mutation (readOnlyHint=false) but no destructive hint. Description adds value by disclosing return format (parsed JSON, literal command), session defaults, and parameter format (PascalCase keys, --cli-input-json). No contradictions with annotations.

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?

Extremely concise and well-structured. First sentence states purpose, followed by parameter guidance, session handling, and alternative tool usage. No redundant words.

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

Completeness5/5

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

Given no output schema, description adequately explains return value (parsed JSON, literal command). Covers session management, parameter format, query filtering, timeouts, and output format. Complements sibling tool list effectively.

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 coverage is 100% with descriptions for all 8 parameters. Description goes beyond schema by explaining the 'params' structure (PascalCase keys, --cli-input-json) and query parameter (JMESPath, reduction hint). Adds useful context for parameter usage.

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?

Clearly states verb 'Run' and resource 'arbitrary AWS API operation via the aws CLI'. Differentiates from sibling high-level tools by explicitly noting this targets low-level API, with an example comparison to 'aws s3 cp'.

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?

Provides explicit guidance on when to use ('targets the low-level API') and when not to ('for high-level wrappers, use your shell'). Mentions session profile/region override. Could be more exhaustive about specific sibling alternatives, but the context is clear.

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

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