Skip to main content
Glama

aws_call

Call any AWS read operation from Describe/Get/List/Filter/Lookup families via boto3, with automatic pagination and read-only enforcement. Mutations need explicit opt-in and a confirmation token.

Instructions

Generic boto3 passthrough for the AWS read surface: call any Describe*/Get*/List*/Filter*/Lookup* operation that isn't pre-wrapped (DescribeSecurityGroupRules, GetIPSet, GetWebACL, FilterLogEvents, DescribeTargetHealth, …). operation is the boto3 snake_case method name; params is the boto3 argument object (PascalCase keys). Reads auto-paginate and run read-only. Mutating ops need mutate=true AND dangerous guard mode. Destructive verbs (delete/terminate/destroy/purge) are refused unless enabled in config, and even then require a two-phase confirm (first call returns a token + summary and does NOT touch AWS; re-call with confirm= to execute). region/account pin the call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mutateNoRequired true to run any non-read operation (including destructive ones).
paramsNoboto3 argument object (PascalCase keys), e.g. {"GroupIds": ["sg-0abc"]}.
regionNoAWS region. Empty uses the configured default region.
accountNoAccount id selecting a per-account control-plane role (optional).
confirmNoSecond-phase confirmation token for a destructive op. Leave empty on the first call to receive a summary + token; re-call with the token to execute.
serviceYesAWS service id, e.g. 'ec2', 'wafv2', 'elbv2', 'logs', 'rds'.
max_itemsNoCap on auto-paginated read items (0 = default 1000).
operationYesboto3 snake_case operation, e.g. 'describe_security_group_rules', 'get_ip_set', 'filter_log_events'.
Behavior5/5

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

No annotations provided, so description carries full burden. It details auto-pagination for reads, read-only default, mutate flag, destructive guard mode with two-phase confirm, and region/account pinning. Very transparent.

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?

Single dense paragraph, front-loaded with purpose. Every sentence adds unique value. No fluff despite complex behavior.

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?

Covers all behavioral aspects (pagination, mutation, destruction safeguards, region/account). No output schema, but return values are implied. Complete for agent to use correctly.

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

Parameters5/5

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

Schema description coverage is 100%, but description adds key context: snake_case operation names, PascalCase params keys, two-phase confirm flow, region/account pinning. Adds meaning beyond schema.

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?

The description clearly states it's a generic boto3 passthrough for specific AWS read operations (Describe*/Get*/List*/Filter*/Lookup*) and also covers mutating/destructive variants. It distinguishes from sibling tools which are pre-wrapped for specific AWS actions.

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

Usage Guidelines5/5

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

Explicitly says when to use: for any non-wrapped read operations, and for mutating ops with mutate=true. Destructive ops require two-phase confirm and config. This gives clear guidelines on usage vs alternatives.

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/zb-ss/servonaut'

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