Skip to main content
Glama
rad-security

RAD Security

Official
by rad-security

list_clusters

Retrieve and display Kubernetes clusters managed by RAD Security for security monitoring and management.

Instructions

List Kubernetes clusters managed by RAD Security

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
page_sizeNoNumber of clusters per page for list_clusters (default: 50)
pageNoPage number to retrieve for list_clusters (default: 1)

Implementation Reference

  • The core handler function that executes the list_clusters tool by calling the RAD Security API to retrieve a paginated list of clusters.
    export async function listClusters(
      client: RadSecurityClient,
      page_size: number = 50,
      page: number = 1,
    ): Promise<any> {
      const params: Record<string, any> = { page_size, page };
      return client.makeRequest(
        `/accounts/${client.getAccountId()}/clusters`,
        params
      );
    }
  • Zod schema defining the input parameters for the list_clusters tool: page_size and page.
    export const ListClustersSchema = z.object({
      page_size: z.number().optional().default(50).describe("Number of clusters per page for list_clusters (default: 50)"),
      page: z.number().optional().default(1).describe("Page number to retrieve for list_clusters (default: 1)"),
    });
  • src/index.ts:150-153 (registration)
    Tool registration in the ListTools response, defining the name, description, and input schema for discovery.
      name: "list_clusters",
      description: "List Kubernetes clusters managed by RAD Security",
      inputSchema: zodToJsonSchema(clusters.ListClustersSchema),
    },
  • src/index.ts:754-768 (registration)
    Handler registration in the CallToolRequest switch statement, parsing args with schema and delegating to the listClusters handler.
    case "list_clusters": {
      const args = clusters.ListClustersSchema.parse(
        request.params.arguments
      );
      const response = await clusters.listClusters(
        client,
        args.page_size,
        args.page
      );
      return {
        content: [
          { type: "text", text: JSON.stringify(response, null, 2) },
        ],
      };
    }
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 states it's a list operation, implying read-only behavior, but does not cover aspects like authentication requirements, rate limits, pagination details beyond schema defaults, or error handling, leaving 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, direct sentence with no unnecessary words, efficiently conveying the core purpose. It is appropriately sized and front-loaded, 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 (list operation with 2 optional parameters) and 100% schema coverage, the description is minimally adequate. However, with no annotations and no output schema, it lacks details on behavioral traits and return values, leaving room for improvement in completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema fully documents the two parameters (page_size and page) with defaults. The description adds no additional parameter semantics beyond what the schema provides, resulting in a baseline score of 3.

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') and resource ('Kubernetes clusters managed by RAD Security'), making the purpose unambiguous. However, it does not differentiate from sibling tools like 'list_cloud_resources' or 'list_k8s_resources' that might also list resources, missing explicit distinction.

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 such as 'list_cloud_resources' or 'get_cluster_details'. The description lacks context about prerequisites, scenarios, or exclusions, offering minimal usage direction.

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/rad-security/mcp-server'

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