Skip to main content
Glama

ledfx_create_backup

Creates a complete backup of LedFX configuration, including virtuals, scenes, playlists, and audio settings. Optionally saves the backup to a local file path.

Instructions

Create a complete backup of LedFX configuration (virtuals, scenes, playlists, audio). Optionally saves to a local file path.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_pathNoLocal file path to save the backup (e.g., '/Users/me/backups/ledfx-backup.json'). If not provided, returns backup in response.
descriptionNoOptional description for the backup (e.g., 'Before major changes', 'DJ setup v2')
Behavior3/5

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

Discloses components of backup and optional local save, but lacks details on overwrite behavior, permissions, or whether the operation is non-destructive. Without annotations, more disclosure would be helpful.

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?

Two concise sentences that front-load the purpose. No wasted words.

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?

With no output schema, description mentions returns backup but not its format or error handling. Adequate for a simple tool with minimal parameters, but could specify return type more clearly.

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 coverage is 100%, so baseline is 3. Description adds value by explaining that not providing file_path returns backup in response, but does not elaborate further on parameter behavior.

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?

Clearly states the action (create), resource (backup of LedFX configuration), and scope (virtuals, scenes, playlists, audio). Distinguishes from sibling tools like restore_backup and validate_backup.

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?

No explicit guidance on when to use this tool vs alternatives like restore_backup or validate_backup. Only implies its use for backup creation without context or exclusions.

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/abossard/ledfx-mcp'

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