Skip to main content
Glama

list_ssm_parameters

Retrieve names of SSM Parameters stored in AWS Systems Manager to manage configuration data across services.

Instructions

Lists SSM Parameters (names only).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler logic for the 'list_ssm_parameters' tool. It sends a DescribeParametersCommand to the SSMClient, extracts parameter names, types, and descriptions, and returns them as JSON.
    if (name === "list_ssm_parameters") {
        // DescribeParameters mainly lists them
        const command = new DescribeParametersCommand({});
        const response = await ssmClient.send(command);
        const params = response.Parameters?.map(p => ({ Name: p.Name, Type: p.Type, Description: p.Description })) || [];
        return { content: [{ type: "text", text: JSON.stringify(params, null, 2) }] };
    }
  • src/index.ts:762-766 (registration)
    Tool registration in the ListToolsRequestSchema handler, including name, description, and input schema (empty object).
    {
        name: "list_ssm_parameters",
        description: "Lists SSM Parameters (names only).",
        inputSchema: { "type": "object", "properties": {} }
    },
  • Initialization of the SSMClient used by the list_ssm_parameters handler.
    const ssmClient = new SSMClient({});
  • Import of SSMClient and DescribeParametersCommand required for the tool implementation.
    import { SSMClient, DescribeParametersCommand } from "@aws-sdk/client-ssm";
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 the output format ('names only'), which is helpful, but lacks critical details such as whether this is a read-only operation, pagination behavior, rate limits, authentication requirements, or error conditions. For a tool with zero annotation coverage, this leaves significant gaps.

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's front-loaded with the core purpose and includes a clarifying detail ('names only') that adds value without verbosity.

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 simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate. It specifies the output scope ('names only'), which is useful, but lacks details on behavioral aspects like pagination or error handling. For a list operation with no structured support, it could be more complete.

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 with 100% schema description coverage, so the schema already fully documents the input (none required). The description doesn't need to add parameter information, and it appropriately doesn't mention any. A baseline of 4 is applied since no parameters exist, and the description doesn't introduce confusion.

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 ('Lists') and resource ('SSM Parameters'), and specifies the scope ('names only'), which provides a specific verb+resource+scope combination. However, it doesn't explicitly differentiate from potential sibling tools (though none appear to be SSM-related in the provided list), so it falls short of a perfect score.

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, prerequisites, or context. It simply states what the tool does without indicating appropriate scenarios or limitations.

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