Skip to main content
Glama

get_common_container_configs

Retrieve pre-configured container definitions for applications like Splunk, Wazuh, ELK, Nginx, PostgreSQL, Redis, and Grafana to use with container templates in cyber range environments.

Instructions

Get pre-configured container definitions for common applications.

Returns a dictionary of common application containers (Splunk, Wazuh, ELK, Nginx, PostgreSQL, Redis, Grafana) that can be used with create_container_template.

Returns: Dictionary of application name to container configuration

Example: # Get all common container configs configs = await get_common_container_configs()

# Use Splunk config to create template
splunk_config = configs["splunk"]
result = await create_container_template(
    name="ubuntu-splunk",
    base_os="ubuntu-22.04",
    containers=[splunk_config]
)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/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 discloses that the tool returns a dictionary of configurations and includes an example, which adds behavioral context. However, it does not mention potential limitations like rate limits, authentication needs, or error conditions. The description is informative but lacks comprehensive behavioral traits beyond the basic return format.

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 and front-loaded with the core purpose, followed by details on returns and an example. Every sentence adds value: the first states the purpose, the second specifies the return format, and the example illustrates usage. It could be slightly more concise by integrating the example more tightly, but overall it is efficient with minimal waste.

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 complexity (simple retrieval with no parameters) and lack of annotations and output schema, the description is moderately complete. It explains what the tool does and provides an example, but does not cover potential errors, side effects, or detailed output structure beyond 'dictionary'. For a tool with no structured metadata, more behavioral context would enhance completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, and the schema description coverage is 100% (empty schema). The description does not need to add parameter semantics, as there are none to document. It appropriately focuses on the output and usage, earning a baseline score of 4 for a parameterless tool.

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: 'Get pre-configured container definitions for common applications.' It specifies the verb ('Get') and resource ('pre-configured container definitions'), and lists the applications covered (Splunk, Wazuh, ELK, etc.). However, it does not explicitly differentiate from sibling tools like 'get_container_config' or 'list_common_containers', which may have overlapping or distinct functions.

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

Usage Guidelines3/5

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

The description implies usage by mentioning that the returned configurations 'can be used with create_container_template' and provides an example. However, it does not explicitly state when to use this tool versus alternatives (e.g., 'get_container_config' for custom configs or 'list_common_containers' for just names). The guidance is contextual but lacks explicit when/when-not instructions.

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/tjnull/Ludus-FastMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server