Skip to main content
Glama
valentinlutun-cmd

Voicebox MCP (Full)

voicebox_update_profile_effects

Update the default effects chain for a voice profile using a profile ID and a JSON string of effect configurations.

Instructions

Update the default effects chain for a voice profile.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
effectsYesJSON string of effect configurations (use voicebox_list_effects to see available types).
profile_idYesThe profile ID.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

With no annotations, the description must carry the full burden of behavioral disclosure. It only says 'Update' without explaining whether the chain is replaced or appended, required permissions, or side effects. This is insufficient for a mutation 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 a single, concise sentence with no redundant words. However, it could benefit from slight expansion to improve completeness without losing conciseness.

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

Completeness2/5

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

Despite having an output schema (unknown content), the description lacks essential context: what 'default effects chain' means, whether the update is incremental or a full replacement, and any prerequisites. The tool is simple but still underexplained.

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?

The input schema already covers both parameters with descriptions (100% coverage). The tool description adds no additional meaning beyond the schema, so the baseline score of 3 is appropriate.

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 'Update' and the resource 'default effects chain for a voice profile'. It is specific and informative, though it doesn't explicitly distinguish from siblings like voicebox_apply_effects or voicebox_update_profile.

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 guidance is provided on when to use this tool versus alternatives such as voicebox_apply_effects, voicebox_preview_effects, or voicebox_update_profile. The agent is left to infer usage from the name and description.

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/valentinlutun-cmd/voicebox-mcp-full'

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