Skip to main content
Glama
rad-security

RAD Security

Official
by rad-security

get_inbox_item_details

Retrieve detailed security findings for a specific inbox item in Kubernetes and cloud environments to analyze potential threats.

Instructions

Get detailed information about a specific inbox item

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inbox_item_idYesID of the inbox item to get details for

Implementation Reference

  • The main handler function that fetches inbox item details from the API, removes unnecessary fields, fetches and attaches comments, and returns the enriched details.
    export async function getInboxItemDetails(
      client: RadSecurityClient,
      inboxItemId: string
    ): Promise<any> {
      var details = await client.makeRequest(
        `/accounts/${client.getAccountId()}/data/inbox_items/${inboxItemId}`
      );
    
      // Remove fields to reduce context window size when used with LLMs data.fields
      delete details.fields;
    
      // fetch all comments for the inbox item
      const comments_params: Record<string, any> = {
        "filters_query": `inbox_item_id:"${inboxItemId}"`
      };
    
      var comments = await client.makeRequest(
        `/accounts/${client.getAccountId()}/data/inbox_item_comments`,
        comments_params
      );
      delete comments.fields;
    
      // add comments to the details
      details.comments = comments;
    
      return details;
    }
  • Zod schema defining the input parameters for the tool: inbox_item_id (string).
    export const GetInboxItemDetailsSchema = z.object({
      inbox_item_id: z.string().describe("ID of the inbox item to get details for"),
    });
  • src/index.ts:496-501 (registration)
    Tool registration in the ListTools handler: defines name, description, and input schema using the imported schema.
    {
      name: "get_inbox_item_details",
      description:
        "Get detailed information about a specific inbox item",
      inputSchema: zodToJsonSchema(inbox.GetInboxItemDetailsSchema),
    },
  • src/index.ts:1371-1384 (registration)
    Tool execution handler in the CallToolRequest switch case: parses args with schema, calls the handler function, and returns JSON response.
    case "get_inbox_item_details": {
      const args = inbox.GetInboxItemDetailsSchema.parse(
        request.params.arguments
      );
      const response = await inbox.getInboxItemDetails(
        client,
        args.inbox_item_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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states this is a read operation ('Get'), but doesn't cover aspects like authentication requirements, rate limits, error handling, or what 'detailed information' includes (e.g., fields, format). This leaves significant gaps for a tool with no annotation support.

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, focused sentence with no wasted words. It's front-loaded with the core action and resource, making it efficient and easy to parse.

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 simple input schema (1 parameter, 100% coverage) and lack of annotations/output schema, the description is minimally adequate. It clarifies the tool's purpose but lacks behavioral details and usage context, which are important for a read operation in a complex environment with many sibling tools.

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?

The schema description coverage is 100%, with the single parameter 'inbox_item_id' fully documented in the schema. The description doesn't add any parameter details beyond what the schema provides (e.g., format examples, sourcing hints), so it meets the baseline of 3 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 ('Get') and resource ('detailed information about a specific inbox item'), making the purpose understandable. However, it doesn't distinguish this tool from potential sibling tools like 'list_inbox_items' or 'get_identity_details' in terms of scope or detail level.

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 inbox item ID from list_inbox_items), exclusions, or comparisons to sibling tools, leaving the agent to infer usage context.

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