Skip to main content
Glama
rad-security

RAD Security

Official
by rad-security

get_top_vulnerable_images

Identify and retrieve the most vulnerable container images from your RAD Security account to prioritize security remediation in Kubernetes and cloud environments.

Instructions

Get the most vulnerable images from your account

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function implementing the tool logic by calling the RAD Security API endpoint for top vulnerable images.
    export async function getTopVulnerableImages(
      client: RadSecurityClient
    ): Promise<any> {
      return client.makeRequest(
        `/accounts/${client.getAccountId()}/reports/top_vulnerable_images`,
        {},
        {
          headers: {
            "Accept": "application/json",
          },
        }
      );
    }
  • src/index.ts:298-301 (registration)
    Tool registration in the listTools handler, defining name, description, and empty input schema.
      name: "get_top_vulnerable_images",
      description: "Get the most vulnerable images from your account",
      inputSchema: zodToJsonSchema(z.object({})),
    },
  • MCP callToolRequest dispatch handler that invokes the getTopVulnerableImages operation and formats the response.
    case "get_top_vulnerable_images": {
      const response = await images.getTopVulnerableImages(client);
      return {
        content: [
          { type: "text", text: JSON.stringify(response, null, 2) },
        ],
      };
    }
  • Inline Zod schema for empty input parameters.
    inputSchema: zodToJsonSchema(z.object({})),
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states a read operation ('Get'), but doesn't disclose behavioral traits like authentication needs, rate limits, pagination, sorting criteria for 'most vulnerable', or what data is returned. This leaves significant gaps for an agent to understand how to use it effectively.

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 no wasted words. It's front-loaded with the core purpose, making it easy to parse quickly.

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 no annotations, no output schema, and a vague purpose, the description is incomplete. It doesn't explain what 'most vulnerable' means, how results are returned, or any constraints. For a tool that likely returns prioritized data, more context is needed to use it correctly.

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 doesn't add param info, which is fine here. Baseline is 4 since it's appropriate for a zero-param tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get the most vulnerable images from your account' states a clear action ('Get') and resource ('most vulnerable images'), but it's vague about what 'most vulnerable' means (by count, severity, recency?). It doesn't distinguish from siblings like 'list_images' or 'list_image_vulnerabilities' which might provide similar functionality.

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 on when to use this tool versus alternatives like 'list_images' or 'list_image_vulnerabilities'. The description implies a filtered or prioritized view, but doesn't specify prerequisites, context, or exclusions for 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/rad-security/mcp-server'

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