Skip to main content
Glama

config_create

Create an immutable Swarm config object to store non-sensitive configuration files and mount them into service containers at a specified path using raw byte data.

Instructions

Create an immutable Swarm config object; requires a swarm manager.

Configs store non-sensitive configuration files (nginx.conf, app.yaml, etc.) and mount them into service containers at a specified path. Unlike secrets, config data is not encrypted at rest — use secret_create for credentials or keys. data is raw bytes; encode strings first (e.g. "my config".encode()). Once created, a config is immutable: to update it, create a new config with a new name and update the service to reference it, then remove the old config with config_remove.

args: name - Unique config name within the swarm data - Raw bytes content of the config file labels - Labels to set on the config templating - Templating driver config (e.g. {"Name": "golang"} for Go template syntax) returns: dict - The created config's attrs ({"ID", "Version", "CreatedAt", "Spec", ...})

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
nameYes
labelsNo
templatingNo
Behavior4/5

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

Annotations (readOnlyHint: false, destructiveHint: false) are basic. The description adds significant behavioral context: configs are immutable, data is raw bytes requiring encoding, and they are mounted into service containers. The only gap is not mentioning any permission or manager requirements explicitly stated upfront, but 'requires a swarm manager' is there.

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?

Description is well-structured with an overview first, then parameter explanations. Slightly verbose with example encoding hint, but each sentence adds value. Could be trimmed slightly without losing clarity.

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

Completeness5/5

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

No output schema, but description mentions return dict keys (ID, Version, etc.). Context covers creation, immutability, update lifecycle, and alternative tool. Agent has all needed info to decide and invoke correctly.

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

Parameters5/5

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

Schema coverage is 0%, so description must explain all parameters. It does: name (unique), data (raw bytes, encoding hint), labels (labels to set), templating (driver config like {'Name': 'golang'}). Adds encoding guidance beyond schema.

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 creates an immutable Swarm config object, distinguishes from secrets by noting encryption differences, and mentions immutability. Sibling tools like secret_create and config_remove are referenced, providing clear differentiation.

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?

Explicitly states when to use config_create vs secret_create: 'Unlike secrets, config data is not encrypted at rest — use secret_create for credentials or keys.' Also explains the update workflow: create new config, update service, remove old. No confusion.

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/GavinLucas/docker-mcp'

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