Skip to main content
Glama
rad-security

RAD Security

Official
by rad-security

get_k8s_resource_misconfig

Retrieve detailed information about specific Kubernetes resource misconfigurations to identify and address security vulnerabilities in your cluster.

Instructions

Get detailed information about a specific Kubernetes resource misconfiguration

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cluster_idYesID of the cluster to get misconfiguration for
misconfig_idYesID of the misconfiguration to get details for

Implementation Reference

  • The handler function that executes the core logic of fetching Kubernetes resource misconfiguration details via API request.
    export async function getKubernetesResourceMisconfigurationDetails(
      client: RadSecurityClient,
      clusterId: string,
      misconfigId: string
    ): Promise<any> {
      const response = await client.makeRequest(
        `/accounts/${client.getAccountId()}/clusters/${clusterId}/misconfig/${misconfigId}`
      );
    
      if (!response) {
        throw new Error(`No misconfiguration found with ID: ${misconfigId}`);
      }
    
      return response;
    }
  • Zod schema defining the input parameters for the tool: cluster_id and misconfig_id.
    export const GetKubernetesResourceMisconfigurationDetailsSchema = z.object({
      cluster_id: z.string().describe("ID of the cluster to get misconfiguration for"),
      misconfig_id: z.string().describe("ID of the misconfiguration to get details for"),
    });
  • src/index.ts:341-347 (registration)
    Registration of the tool in the MCP server's listTools response, including name, description, and input schema reference.
      name: "get_k8s_resource_misconfig",
      description:
        "Get detailed information about a specific Kubernetes resource misconfiguration",
      inputSchema: zodToJsonSchema(
        misconfigs.GetKubernetesResourceMisconfigurationDetailsSchema
      ),
    },
  • src/index.ts:1108-1124 (registration)
    Handler registration in the MCP server's CallToolRequest switch statement, parsing args and calling the implementation function.
    case "get_k8s_resource_misconfig": {
      const args =
        misconfigs.GetKubernetesResourceMisconfigurationDetailsSchema.parse(
          request.params.arguments
        );
      const response =
        await misconfigs.getKubernetesResourceMisconfigurationDetails(
          client,
          args.cluster_id,
          args.misconfig_id
        );
      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 full burden but only states it 'gets detailed information' without disclosing behavioral traits. It doesn't mention if this is a read-only operation, what format the details are in (e.g., JSON structure), potential errors (e.g., invalid IDs), or any rate limits. This leaves significant gaps for a tool that likely returns complex security data.

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 directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, with every part contributing to clarity.

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 complexity of Kubernetes security misconfigurations and the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'detailed information' includes (e.g., severity, remediation steps), the response format, or error handling. For a tool with no structured output documentation, this leaves too much unspecified.

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%, with both parameters clearly documented in the schema. The description adds no additional meaning beyond implying these IDs are needed to fetch details, which is already covered. This meets the baseline of 3 when the schema does the heavy lifting.

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 'Get' and the resource 'detailed information about a specific Kubernetes resource misconfiguration', making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'list_k8s_resource_misconfigs' or 'get_k8s_resource_details', which would require mentioning this retrieves details for a specific misconfiguration ID rather than listing multiple.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites like needing a specific misconfiguration ID from a list operation, nor does it compare to siblings like 'list_k8s_resource_misconfigs' for browsing or 'get_k8s_resource_details' for general resource info.

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