Skip to main content
Glama
YawLabs

@yawlabs/aws-mcp

Official
by YawLabs

aws_resource_create

Create AWS resources via Cloud Control API. Returns a progress token for async polling, or optionally waits for completion with built-in polling.

Instructions

Create an AWS resource via Cloud Control API. Async by default: returns a ProgressEvent with OperationStatus=IN_PROGRESS and a requestToken (top-level) -- poll aws_resource_status with that token, or pass awaitCompletion: true to have the server poll for you and return the terminal event. desiredState is the resource properties JSON matching the CloudFormation schema for typeName.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNameYesCloudFormation type name, e.g. 'AWS::SSM::Parameter'.
desiredStateYesResource properties matching the CFN schema. E.g. for AWS::SSM::Parameter: {Name: '/my/param', Type: 'String', Value: 'hello'}.
clientTokenNoIdempotency token (max 128 chars). Prevents duplicate creation on retry.
profileNoOverride session profile for this call.
regionNoOverride session region for this call.
timeoutMsNoTimeout in milliseconds. Default 60000.
awaitCompletionNoIf true, poll get-resource-request-status until the operation reaches SUCCESS / FAILED / CANCEL_COMPLETE and return the final ProgressEvent. Default false (returns immediately with IN_PROGRESS, caller polls via aws_resource_status).
pollIntervalMsNoPoll interval in ms when awaitCompletion is true (range 500-30000). Default 2000. ProgressEvent.RetryAfter overrides when CCAPI returns one.
maxWaitMsNoMaximum total wait in ms when awaitCompletion is true (range 1000-1800000). Default 300000. On timeout, returns the last seen status with a hint to keep polling.
Behavior5/5

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

Annotations provide readOnlyHint false, destructiveHint false, idempotentHint false. Description adds async behavior, ProgressEvent return, polling details, and idempotency via clientToken. No contradictions.

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?

Concise yet informative. Sentences are direct and front-loaded with key behavior. Could be slightly more structured, but 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?

No output schema, but description explains return value (ProgressEvent). Covers 9 parameters adequately. For a creation tool with async behavior, completeness is good.

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%. Description expands on awaitCompletion, pollIntervalMs, maxWaitMs with clear behavior. DesiredState format example helps.

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 it creates an AWS resource via Cloud Control API. Distinguishes from sibling tools like aws_resource_delete and aws_resource_update. Mentions async behavior and polling.

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?

Describes async default and awaitCompletion option. Advises polling via aws_resource_status. Does not explicitly state when not to use, but context is sufficient.

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