Skip to main content
Glama
rad-security

RAD Security

Official
by rad-security

list_dashboard_templates

Browse available dashboard templates for security insights, with options to filter by category and paginate results.

Instructions

List dashboard templates with optional filtering by category

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results to return (default: 10, min: 1)
offsetNoPagination offset (default: 0, min: 0)
categoryNoFilter by category

Implementation Reference

  • Core handler function that executes the tool logic by calling the RAD Security API to list dashboard templates.
    /**
     * List dashboard templates with optional filtering.
     */
    export async function listDashboardTemplates(
      client: RadSecurityClient,
      limit: number = 50,
      offset: number = 0,
      category?: string
    ): Promise<any> {
      const params: Record<string, any> = { limit, offset };
    
      if (category) {
        params.category = category;
      }
    
      return client.makeRequest(
        `/accounts/${client.getAccountId()}/dashboards/templates`,
        params
      );
    }
  • Zod input schema used for validation in both tool listing and execution.
    // Schema for list_dashboard_templates
    export const ListDashboardTemplatesSchema = z.object({
      limit: z.number().optional().default(10).describe("Maximum number of results to return (default: 10, min: 1)"),
      offset: z.number().optional().default(0).describe("Pagination offset (default: 0, min: 0)"),
      category: z.string().optional().describe("Filter by category"),
    });
  • src/index.ts:668-675 (registration)
    Tool registration in the list_tools handler, defining name, description, and input schema.
    {
      name: "list_dashboard_templates",
      description:
        "List dashboard templates with optional filtering by category",
      inputSchema: zodToJsonSchema(
        dashboards.ListDashboardTemplatesSchema
      ),
    },
  • src/index.ts:1628-1642 (registration)
    Tool handler dispatch in the call_tool request handler, parsing args and invoking the core handler.
    case "list_dashboard_templates": {
      const args = dashboards.ListDashboardTemplatesSchema.parse(
        request.params.arguments
      );
      const response = await dashboards.listDashboardTemplates(
        client,
        args.limit,
        args.offset,
        args.category
      );
      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. It mentions 'optional filtering by category' but doesn't disclose other behavioral traits like pagination behavior (implied by limit/offset in schema), rate limits, authentication needs, error handling, or what the return format looks like. For a list tool with no annotation coverage, this is a significant gap.

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 zero waste. It's front-loaded with the core purpose and includes a key feature (filtering). Every word earns its place, making it appropriately sized for a simple list tool.

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 low complexity (a list operation with filtering and pagination), no annotations, and no output schema, the description is minimally adequate. It covers the basic purpose and filtering feature, but lacks details on return values, error cases, or behavioral context. It's complete enough for a simple tool but leaves gaps an agent might need.

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 all three parameters (limit, offset, category). The description adds minimal value by mentioning 'optional filtering by category', which aligns with the schema but doesn't provide additional syntax or format details. 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 ('List') and resource ('dashboard templates'), and mentions optional filtering by category. It distinguishes from siblings like 'get_dashboard_template' (singular) by indicating it returns multiple items. However, it doesn't explicitly differentiate from other list tools like 'list_dashboards' or 'list_widget_templates' beyond the resource type.

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, compare with similar tools like 'list_dashboards' or 'get_dashboard_template', or specify use cases. The only contextual hint is 'optional filtering by category', which is a feature but not a usage guideline.

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