Skip to main content
Glama
rad-security

RAD Security

Official
by rad-security

list_containers

Retrieve and filter containers secured by RAD Security using image name, digest, namespace, cluster ID, or free text search to monitor Kubernetes security.

Instructions

List containers secured by RAD Security with optional filtering by image name, image digest, namespace, cluster_id, or free text search

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filtersNoFilter string (e.g., 'image_name:nginx' or 'image_digest:sha256:...' or 'owner_namespace:namespace' or 'cluster_id:cluster_id'). Multiple filters can be combined with commas.
offsetNoPagination offset. Default: 0
limitNoMaximum number of results to return. Default: 20
qNoFree text search query

Implementation Reference

  • The handler function that executes the logic for listing containers by making an API request to the RAD Security client and processing the response.
    export async function listContainers(
      client: RadSecurityClient,
      offset: number = 0,
      limit: number = 20,
      filters?: string,
      q?: string
    ): Promise<any> {
      const params: Record<string, any> = { limit, offset, filters, q };
      const response = await client.makeRequest(`/accounts/${client.getAccountId()}/inventory_containers`, params);
    
      // Remove "id" from each container to avoid confusion
      response.entries.forEach((container: any) => {
        delete container.id;
      });
    
      return response;
    }
  • Zod schema defining the input parameters for the list_containers tool.
    export const ListContainersSchema = z.object({
      filters: z.string().optional().describe("Filter string (e.g., 'image_name:nginx' or 'image_digest:sha256:...' or 'owner_namespace:namespace' or 'cluster_id:cluster_id'). Multiple filters can be combined with commas."),
      offset: z.number().optional().describe("Pagination offset. Default: 0"),
      limit: z.number().optional().describe("Maximum number of results to return. Default: 20"),
      q: z.string().optional().describe("Free text search query"),
    });
  • src/index.ts:130-135 (registration)
    Registration of the list_containers tool in the listTools handler, including name, description, and schema.
    {
      name: "list_containers",
      description:
        "List containers secured by RAD Security with optional filtering by image name, image digest, namespace, cluster_id, or free text search",
      inputSchema: zodToJsonSchema(containers.ListContainersSchema),
    },
  • src/index.ts:722-737 (registration)
    Dispatch handler in the callToolRequest that parses arguments, calls the listContainers function, and returns the response for the list_containers tool.
    case "list_containers": {
      const args = containers.ListContainersSchema.parse(
        request.params.arguments
      );
      const response = await containers.listContainers(
        client,
        args.offset,
        args.limit,
        args.filters,
        args.q
      );
      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 implies a read-only operation ('List') but doesn't specify if it's safe, requires authentication, has rate limits, or what the output format looks like. The mention of 'secured by RAD Security' hints at security context but lacks details on access controls or potential side effects.

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 and lists filtering options without unnecessary words. Every part of the sentence contributes directly to understanding the tool's functionality.

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 complexity (listing with multiple filters and pagination), no annotations, and no output schema, the description is adequate but incomplete. It covers the basic purpose and parameters but lacks behavioral details like pagination behavior, error handling, or security requirements, which are important for a tool in a security context.

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 all parameters. The description adds minimal value by listing filterable attributes (image name, digest, namespace, cluster_id, free text search), but doesn't explain syntax or usage beyond what's in the schema. This meets the baseline for high schema coverage.

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 ('List') and resource ('containers secured by RAD Security'), making the purpose evident. It distinguishes from siblings like 'get_container_details' by focusing on listing with filtering rather than retrieving details. However, it doesn't explicitly differentiate from 'list_images' or 'list_k8s_resources', which could involve overlapping 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?

The description mentions optional filtering but provides no guidance on when to use this tool versus alternatives like 'list_images' or 'get_container_details'. It lacks context on prerequisites, such as whether specific permissions are needed, or when filtering is appropriate versus other listing tools.

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