Skip to main content
Glama

NS Pros MCP Gateway

aws-mcp__aws___list_regions

Retrieve a list of all AWS regions.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "aws-mcp__aws___list_regions"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden, and it does convey the two most important traits indirectly: 'Retrieve' signals a read-only operation and 'all' signals an unfiltered, presumably unpaginated result. It says nothing about whether opt-in/disabled regions are included, what identifiers are returned (region names vs. codes), or any ordering or rate-limit behavior.

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?

A single self-contained sentence with no filler, and the resource being listed is front-loaded. Nothing in it is redundant with the tool name or could be trimmed without losing meaning.

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

Completeness3/5

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

There is no output schema and no annotations, so the description is the only source of truth, and it omits the shape of the returned data (e.g., a bare array of region identifier strings) that an agent needs to consume the result. For a trivial zero-argument lister this is a modest but real gap rather than a fatal one.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly does not invent parameter language for an argument-free call.

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 ('Retrieve') and resource ('a list of all AWS regions'), so there is no ambiguity about what the tool returns. It does not, however, differentiate itself from the sibling aws-mcp__aws___get_regional_availability, which an agent could easily confuse with a plain region list.

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?

Usage is only implied: 'list of all AWS regions' suggests this is the enumeration primitive to call before any region-scoped operation. There is no explicit when-to-use statement, no mention of when to prefer get_regional_availability instead, and no stated prerequisites such as credentials.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.