Skip to main content
Glama
rad-security

RAD Security

Official
by rad-security

radql_query

Execute RadQL queries to filter, search, and analyze security data in Kubernetes environments for investigations and aggregations.

Instructions

Execute RadQL queries for security investigations. Supports: list (filter/search), get_by_id (single item), stats (aggregations).

WORKFLOW: radql_list_data_types -> radql_get_type_metadata -> radql_query

COMMON FIELDS BY DATA TYPE: containers: name, image_name, image_repo, owner_kind, cluster_id, created_at Example: image_name:nginx AND owner_kind:Pod

finding_groups: type, source_kind, source_name, rule_title, severity, event_timestamp Types: k8s_misconfiguration, k8s_audit_logs_anomaly, threat_vector Example: type:k8s_misconfiguration AND severity:critical

inbox_items: severity (High|Medium|Low), type, title, archived, false_positive, created_at Example: severity:High AND archived:false

kubernetes_resources: kind, name, namespace, cluster_id, owner_kind, created_at Example: kind:Deployment AND namespace:production

CRITICAL QUOTING RULES: MUST quote when value contains:

  • Dates/timestamps: created_at>"2024-01-01" (NOT created_at>2024-01-01)

  • Hyphens: cluster_id:"abc-123-def", name:"kube-system"

  • UUIDs: id:"550e8400-e29b-41d4-a716-446655440000"

  • Spaces: title:"my alert"

  • Special chars: :, =, <, >, !, (, )

  • Wildcards with hyphens: name:"kube-*"

OK to leave unquoted:

  • Simple strings: status:active, kind:Pod

  • Numbers: count:123

  • Booleans: archived:true

  • Simple wildcards: name:nginx*

For complete schema: call radql_get_type_metadata with target data_type

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
data_typeYesThe data type to query (e.g., 'containers', 'kubernetes_resources', 'inbox_items'). Use radql_list_data_types to discover available types.
operationYesThe operation to perform: 'list' for filtering/searching, 'get_by_id' for single item, 'stats' for aggregations
filters_queryNoRadQL filter query (e.g., 'severity:High AND type:misconfiguration'). Used for filtering results.
stats_queryNoRadQL analytics query (e.g., 'count() by severity'). Used for aggregations and grouping.
idNoThe ID of a specific item to retrieve (for get_by_id operation)
limitNoMaximum number of results to return
offsetNoPagination offset
include_relationsNoRelations to include (e.g., ['owner'] for containers to include Kubernetes owner resource)
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes critical behavioral traits: it explains the query language syntax, provides examples, details quoting rules for values, and outlines common fields by data type. However, it doesn't mention rate limits, authentication needs, or error handling, which are important for a query tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with sections for purpose, workflow, common fields, examples, and quoting rules, making it easy to scan. However, it is quite lengthy due to the detailed examples and rules, which may be necessary but could be optimized. Every sentence adds value, but the front-loading could be improved by summarizing key points first.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of the tool (8 parameters, no annotations, no output schema), the description is mostly complete. It covers purpose, usage, examples, and critical syntax rules. However, it lacks details on output format, error cases, or performance considerations, which would enhance completeness for such a versatile query tool.

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 already documents all 8 parameters thoroughly. The description adds some value by providing context on how parameters like 'filters_query' and 'stats_query' are used with examples, but it doesn't add significant semantic details beyond what the schema provides. The baseline of 3 is appropriate 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.

Purpose5/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: 'Execute RadQL queries for security investigations.' It specifies the supported operations (list, get_by_id, stats) and distinguishes it from siblings by focusing on RadQL query execution rather than specific resource retrieval like the many 'get_' and 'list_' tools. The description provides a specific verb ('Execute') and resource ('RadQL queries') with clear scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly provides usage guidance: it outlines a workflow ('radql_list_data_types -> radql_get_type_metadata -> radql_query'), mentions when to use alternatives ('For complete schema: call radql_get_type_metadata'), and distinguishes operations within the tool (list vs. get_by_id vs. stats). This gives clear context on when and how to use this tool versus others.

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