Skip to main content
Glama

list_eks_clusters

Retrieve Amazon EKS clusters in your current AWS region to monitor and manage Kubernetes environments.

Instructions

Lists EKS clusters in the current region.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'list_eks_clusters' tool. It uses the EKSClient to send a ListEksClustersCommand and returns the list of EKS cluster names as JSON.
    if (name === "list_eks_clusters") {
        const command = new ListEksClustersCommand({});
        const response = await eksClient.send(command);
        return { content: [{ type: "text", text: JSON.stringify(response.clusters || [], null, 2) }] };
    }
  • src/index.ts:732-734 (registration)
    Registration of the 'list_eks_clusters' tool in the list of tools returned by ListToolsRequestHandler.
    name: "list_eks_clusters",
    description: "Lists EKS clusters in the current region.",
    inputSchema: { "type": "object", "properties": {} }
  • Input schema for the 'list_eks_clusters' tool (empty object, no parameters).
    inputSchema: { "type": "object", "properties": {} }
  • Initialization of the EKSClient used by the handler.
    const eksClient = new EKSClient({});
  • Import of EKSClient and ListEksClustersCommand (aliased from ListClustersCommand).
    import { EKSClient, ListClustersCommand as ListEksClustersCommand, DescribeClusterCommand } from "@aws-sdk/client-eks";
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 region scope but does not cover critical aspects like authentication requirements, rate limits, pagination behavior, error handling, or the format of returned data (e.g., cluster names, statuses). This leaves significant gaps for a tool that interacts with AWS services.

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 core purpose ('Lists EKS clusters') and adds necessary scope ('in the current region'). There is no wasted verbiage or unnecessary elaboration, making it highly concise and well-structured.

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 lack of annotations and output schema, the description is incomplete. It does not address behavioral traits (e.g., authentication, pagination) or output details (e.g., what data is returned), which are essential for an AWS listing tool. While concise, it fails to provide sufficient context for safe and effective use by an AI agent.

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 does not add parameter details, and the baseline score is 4 as it avoids redundancy while confirming the tool operates without inputs in the current region context.

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 ('EKS clusters'), specifying the scope as 'in the current region'. However, it does not differentiate from sibling tools like 'list_ecs_clusters' or 'list_ec2_instances', which follow similar naming patterns but target different AWS resources.

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 lacks context about prerequisites (e.g., AWS authentication, region configuration) or comparisons to other listing tools, such as 'list_ecs_clusters' for ECS resources or 'list_ec2_instances' for EC2 instances.

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