Skip to main content
Glama

list_unused_ebs_volumes

Identify and list unattached Amazon EBS volumes to help optimize AWS costs and resource management.

Instructions

Lists EBS volumes that are available (not attached to any instance).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for 'list_unused_ebs_volumes' tool: Queries EC2 for volumes with status 'available' (unused/not attached), maps to relevant fields, and returns JSON.
    if (name === "list_unused_ebs_volumes") {
        const command = new DescribeVolumesCommand({
            Filters: [{ Name: "status", Values: ["available"] }]
        });
        const response = await ec2Client.send(command);
    
        const volumes = response.Volumes?.map(v => ({
            VolumeId: v.VolumeId,
            Size: v.Size,
            Type: v.VolumeType,
            CreateTime: v.CreateTime,
            AvailabilityZone: v.AvailabilityZone
        })) || [];
    
        return {
            content: [{ type: "text", text: JSON.stringify(volumes, null, 2) }]
        };
    }
  • src/index.ts:432-438 (registration)
    Registration of the tool in the ListTools response, including name, description, and empty input schema (no parameters required).
        name: "list_unused_ebs_volumes",
        description: "Lists EBS volumes that are available (not attached to any instance).",
        inputSchema: {
            type: "object",
            properties: {}
        }
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the tool lists volumes, but doesn't disclose behavioral traits such as whether it requires authentication, rate limits, pagination, error handling, or the format of returned data. For a read operation with zero annotation coverage, 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 that front-loads the key information ('Lists EBS volumes') and adds a clarifying condition ('that are available'). There is no wasted text, making it easy for an agent 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 has no parameters and no output schema, the description is minimally adequate. It explains what the tool does but lacks context on authentication, data format, or error handling. For a simple list operation, this might suffice, but without annotations, it leaves the agent to guess about behavioral aspects.

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 appropriately adds no parameter details, focusing instead on the tool's purpose. This meets the baseline for tools with no parameters.

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 ('EBS volumes'), specifying they must be 'available (not attached to any instance)'. It distinguishes from siblings like 'list_ec2_instances' by focusing on unused volumes, though it doesn't explicitly differentiate from other volume-related tools (none exist in the sibling list).

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. The description implies it's for finding unattached volumes, but it doesn't mention prerequisites (e.g., AWS permissions), typical use cases (e.g., cost optimization), or what to do with the results. Without annotations or context, the agent must infer usage.

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