Skip to main content
Glama
rad-security

RAD Security

Official
by rad-security

get_dashboard

Retrieve detailed information about a specific security dashboard to monitor Kubernetes and cloud environment insights from RAD Security.

Instructions

Get detailed information about a specific dashboard

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dashboard_idYesID of the dashboard

Implementation Reference

  • The handler function that implements the core logic of the 'get_dashboard' tool by calling the RAD Security API to retrieve details for a specific dashboard.
    /**
     * Get details for a specific dashboard.
     */
    export async function getDashboard(
      client: RadSecurityClient,
      dashboard_id: string
    ): Promise<any> {
      return client.makeRequest(
        `/accounts/${client.getAccountId()}/dashboards/${dashboard_id}`
      );
    }
  • Zod schema defining the input validation for the 'get_dashboard' tool, requiring a dashboard_id string.
    export const GetDashboardSchema = z.object({
      dashboard_id: z.string().describe("ID of the dashboard"),
    });
  • src/index.ts:689-694 (registration)
    Registration of the 'get_dashboard' tool in the ListToolsRequestSchema handler, specifying name, description, and input schema.
    {
      name: "get_dashboard",
      description:
        "Get detailed information about a specific dashboard",
      inputSchema: zodToJsonSchema(dashboards.GetDashboardSchema),
    },
  • src/index.ts:1673-1685 (registration)
    Execution handler for the 'get_dashboard' tool in the CallToolRequestSchema switch statement, which parses input, calls the handler function, and formats the response.
    case "get_dashboard": {
      const args = dashboards.GetDashboardSchema.parse(
        request.params.arguments
      );
      const response = await dashboards.getDashboard(
        client,
        args.dashboard_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. While 'Get detailed information' implies a read-only operation, it doesn't specify authentication requirements, rate limits, error conditions, or the format/scope of the returned information. For a tool with no annotation coverage, this leaves significant behavioral gaps.

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 for a simple retrieval tool and front-loaded with the essential information.

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 simplicity (one parameter, no output schema, no annotations), the description is minimally adequate. It states what the tool does but lacks behavioral details that would be helpful without annotations. For a basic read operation, it's complete enough to understand the core function but could provide more context about the returned data.

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 input schema has 100% description coverage, with the single parameter 'dashboard_id' clearly documented in the schema. The description adds no additional parameter semantics beyond what's in the schema, so it meets the baseline of 3 where 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 tool's purpose with a specific verb ('Get') and resource ('detailed information about a specific dashboard'), making it immediately understandable. However, it doesn't distinguish this tool from its sibling 'list_dashboards' or other 'get_' tools that retrieve specific resources, which prevents a perfect score.

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 the sibling 'list_dashboards' for browsing dashboards or clarify that this tool is for retrieving details of a single, known dashboard. Without any usage context or exclusions, the agent must infer when this tool is appropriate.

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