Skip to main content
Glama
zb-ss

Servonaut

by zb-ss
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

aws_list_regions

List all AWS regions enabled on an AWS account to discover where resources can be deployed; optionally specify account and bootstrap region.

Instructions

List all AWS regions enabled on the account. bootstrap_region is only used to construct the EC2 client (the call itself is global). Defaults to us-east-1.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountNoAWS account label to act in; omit for the default account.
bootstrap_regionNoRegion used to bootstrap the EC2 client (default: us-east-1).us-east-1

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.28.0
    • addedInput schema / properties / account
      Added value: +{
+  "description": "AWS account label to act in; omit for the default account.",
+  "type": "string"
+}
  2. Addedv2.24.0
  3. Removedv2.23.8
  4. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description must carry the behavioral burden, and it discloses the genuinely non-obvious trait that the list call is global and the region parameter does not scope the result. It stops short of describing return format or any auth/permission requirements, so it is helpful but not fully 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?

Three tight sentences with the core purpose front-loaded and no filler; each sentence adds distinct information (what it lists, how bootstrap_region is used, and its default).

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?

For a simple two-parameter list tool with no output schema and no annotations, the description covers purpose and the key parameter behavior adequately. It could note the return shape or permissions, but nothing essential is missing for correct invocation.

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%, so the baseline is 3, but the description adds meaning beyond the schema by explaining that bootstrap_region only bootstraps the EC2 client and does not affect the global call. That clarifies the parameter's real effect, which the schema text alone does not convey.

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?

The description states a specific verb (List) and resource (AWS regions) and scopes it to those 'enabled on the account', so the operation is unambiguous. It does not explicitly reference a sibling, but no other sibling tool lists regions, so disambiguation is effectively achieved by the name and phrasing.

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?

It clarifies a usage-critical point -- that bootstrap_region only affects client construction and the call itself is global -- which helps an agent invoke it correctly. However, it gives no explicit when-to-use/when-not guidance or alternatives among the many aws_* siblings, so usage is only implied.

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