Skip to main content
Glama
@yawlabs/aws-mcp

@yawlabs/aws-mcp

Official
by YawLabs

aws_list_profiles

Read-onlyIdempotent

Lists AWS profiles from the AWS config file, returning names, regions, and SSO metadata so users can choose or switch profiles and resolve SSO-expired profile errors.

Instructions

List AWS profiles configured in the AWS config file (AWS_CONFIG_FILE, else ~/.aws/config). Returns profile name, region, and SSO metadata (start URL, region, session name) where set, plus an isSso flag. Use when the user hasn't named a profile, when they ask to switch profiles, or when an SSO-expired error mentions a profile you haven't seen.

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_list_profiles"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.2

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=false, so the safety profile is covered. The description adds genuine value beyond that by disclosing the resolution order of the config file (AWS_CONFIG_FILE, else ~/.aws/config) and the shape of each returned entry. It stops short of noting limits such as whether credentials files or multiple profile sources are consulted.

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 sentences, front-loaded with what is listed and where it comes from, then the return payload, then the routing triggers. Every clause contributes; nothing is redundant with the name or the annotations.

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?

With no parameters and no output schema, the description carries the return-value burden itself and does so by naming the fields and the isSso flag. Nothing an agent needs in order to call this correctly or interpret the result is missing.

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 per the rubric the baseline is 4. The description correctly implies a no-argument call by framing the source purely as environment/file resolution that the caller does not control.

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?

States a specific verb and resource ("List AWS profiles configured in the AWS config file"), names the config-file precedence in parentheses, and enumerates exactly what comes back (profile name, region, SSO metadata, isSso flag). It never names a sibling such as aws_sso_generate_profiles to draw the contrast explicitly, which keeps it just below a 5.

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?

Gives three concrete triggering conditions: the user hasn't named a profile, the user asks to switch profiles, or an SSO-expired error references an unfamiliar profile. That is solid when-to-use guidance, but there is no when-not clause and no named alternative for the adjacent cases (e.g. generating profiles).

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