Skip to main content
Glama
rad-security

RAD Security

Official
by rad-security

get_identity_details

Retrieve detailed security information about specific identities in Kubernetes clusters to assess access permissions and potential risks.

Instructions

Get detailed information about a specific identity in a Kubernetes cluster

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
identity_idYesIdentity ID to get details for

Implementation Reference

  • The main handler function that implements the core logic of the 'get_identity_details' tool by making an API request to the RAD Security backend to fetch details for the given identity ID.
    export async function getIdentityDetails(
        client: RadSecurityClient,
        identityId: string
      ): Promise<any> {
        const identity = await client.makeRequest(
          `/accounts/${client.getAccountId()}/identities/${identityId}`
        );
    
        if (!identity) {
          throw new Error(`No identity found with ID: ${identityId}`);
        }
    
        return identity;
      }
  • Zod schema for input validation of the tool, requiring an 'identity_id' string parameter.
    export const GetIdentityDetailsSchema = z.object({
      identity_id: z.string().describe("Identity ID to get details for"),
    });
  • src/index.ts:172-176 (registration)
    Registration of the tool in the MCP server's listTools handler, defining its name, description, and input schema.
      name: "get_identity_details",
      description:
        "Get detailed information about a specific identity in a Kubernetes cluster",
      inputSchema: zodToJsonSchema(identities.GetIdentityDetailsSchema),
    },
  • src/index.ts:802-815 (registration)
    Dispatch handler in the MCP server's CallToolRequest handler that validates input with the schema, invokes the tool handler, and returns the JSON response.
    case "get_identity_details": {
      const args = identities.GetIdentityDetailsSchema.parse(
        request.params.arguments
      );
      const response = await identities.getIdentityDetails(
        client,
        args.identity_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 offers minimal behavioral insight. It implies a read-only operation but doesn't disclose authentication needs, rate limits, error conditions, or what 'detailed information' entails (e.g., format, depth). For a tool with zero annotation coverage, this is inadequate.

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 without unnecessary words. It avoids redundancy and wastes no space, 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 and no output schema, the description is insufficient for a tool that presumably returns complex identity details. It doesn't explain the return format, error handling, or dependencies, leaving significant gaps in understanding how to interpret results.

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 single parameter 'identity_id'. The description adds no additional parameter context beyond implying it fetches details for a specific identity, meeting the baseline for high schema coverage without extra value.

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 ('Get detailed information') and resource ('about a specific identity in a Kubernetes cluster'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'list_identities' or 'get_k8s_resource_details', which would require more specific scoping to earn a 5.

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 (e.g., needing an identity ID from 'list_identities'), contrast with bulk retrieval tools, or specify use cases, leaving the agent to infer usage from the name alone.

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