Skip to main content
Glama

list_secrets

Retrieve names of AWS Secrets Manager secrets to manage sensitive data access and configuration across cloud applications.

Instructions

Lists Secrets Manager secrets (names only).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function that executes the list_secrets tool: sends ListSecretsCommand to SecretsManagerClient and formats response with secret names and descriptions.
    if (name === "list_secrets") {
        const command = new ListSecretsCommand({});
        const response = await secretsManagerClient.send(command);
        const secrets = response.SecretList?.map(s => ({ Name: s.Name, Description: s.Description })) || [];
        return { content: [{ type: "text", text: JSON.stringify(secrets, null, 2) }] };
    }
  • src/index.ts:758-761 (registration)
    Registers the list_secrets tool in the ListTools response, including name, description, and input schema (no parameters).
        name: "list_secrets",
        description: "Lists Secrets Manager secrets (names only).",
        inputSchema: { "type": "object", "properties": {} }
    },
  • Initializes the SecretsManagerClient instance used by the list_secrets handler.
    const secretsManagerClient = new SecretsManagerClient({});
  • Imports the SecretsManagerClient class and ListSecretsCommand used for list_secrets implementation.
    import { SecretsManagerClient, ListSecretsCommand } from "@aws-sdk/client-secrets-manager";
Behavior2/5

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

With no annotations provided, the description carries full burden but only states it lists secrets (names only). It doesn't disclose behavioral traits like pagination, rate limits, authentication needs, error conditions, or what 'names only' entails (e.g., no metadata). This leaves significant gaps in understanding how the tool behaves.

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 with zero waste—it directly states the tool's function and scope. It's front-loaded and appropriately sized for a simple list operation, making it easy to parse quickly.

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?

Given the tool's low complexity (0 params, no output schema) and lack of annotations, the description is minimally adequate but incomplete. It covers the basic purpose but misses behavioral details like output format or constraints, which could be important for a list operation in a security context like Secrets Manager.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add param info, which is appropriate here, and the baseline for 0 params is 4, as it doesn't need to compensate for any schema gaps.

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 verb ('Lists') and resource ('Secrets Manager secrets') with a specific scope ('names only'), making the purpose unambiguous. It doesn't distinguish from siblings since there are no other secret-related tools in the list, but it's sufficiently specific for its context.

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?

No guidance is provided on when to use this tool versus alternatives or in what context. The description only states what it does, without mentioning prerequisites, limitations, or comparison to other tools, leaving usage decisions entirely to the agent.

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/bhaveshopss/MCP-server'

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