Skip to main content
Glama

list-credentials

View configured AWS credentials and profiles on your machine to manage access for AWS MCP Server interactions.

Instructions

List all AWS credentials/configs/profiles that are configured/usable on this machine

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • index.ts:81-89 (registration)
    Registers the 'list-credentials' tool in the listTools response with an empty input schema.
      name: "list-credentials",
      description:
        "List all AWS credentials/configs/profiles that are configured/usable on this machine",
      inputSchema: {
        type: "object",
        properties: {},
        required: [],
      },
    },
  • Executes the 'list-credentials' tool by serializing and returning the list of available AWS profile names along with any error from loading credentials.
    } else if (name === "list-credentials") {
      return createTextResponse(
        JSON.stringify({ profiles: Object.keys(profiles), error })
      );
  • Core helper function that loads AWS credentials and configuration files using AWS.IniLoader, merges them into a profiles object, and handles errors.
    async function listCredentials() {
      let credentials: any;
      let configs: any;
      let error: any;
      try {
        credentials = new AWS.IniLoader().loadFrom({});
      } catch (error) {
        error = `Failed to load credentials: ${error}`;
      }
      try {
        configs = new AWS.IniLoader().loadFrom({ isConfig: true });
      } catch (error) {
        error = `Failed to load configs: ${error}`;
      }
    
      const profiles = { ...(credentials || {}), ...(configs || {}) };
    
      return { profiles, error };
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions that credentials are 'configured/usable on this machine', hinting at local scope, but fails to detail critical aspects like whether this is a read-only operation, potential side effects, error handling, or output format, which are essential for safe and effective use.

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?

The description is a single, efficient sentence that directly states the tool's function without unnecessary words. It is front-loaded with the core action and resource, making it easy to parse and understand quickly.

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

Completeness2/5

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

Given the tool's simplicity (0 parameters, no output schema) and lack of annotations, the description is minimal. While it covers the basic purpose, it omits important contextual details such as the output structure, potential errors, or how it interacts with sibling tools, making it incomplete for reliable agent operation.

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 has 0 parameters, and the schema description coverage is 100%, so there is no need for parameter documentation in the description. The description appropriately focuses on the tool's purpose without redundant parameter details, aligning with the baseline expectation for parameterless tools.

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 clearly states the action ('List all') and the resource ('AWS credentials/configs/profiles'), making the tool's purpose evident. However, it does not explicitly differentiate from sibling tools like 'select-profile', which might involve similar resources but different actions, leaving room for minor ambiguity.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives such as 'select-profile' or 'run-aws-code'. It lacks context about prerequisites, scenarios for usage, or exclusions, leaving the agent without clear direction on tool selection.

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/ihatesea69/AWS-MCP'

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