Skip to main content
Glama
valentinlutun-cmd

Voicebox MCP (Full)

voicebox_upload_avatar

Assign an avatar image to a voice profile by providing the profile ID and the absolute path to the image file.

Instructions

Upload an avatar image for a voice profile.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
image_pathYesAbsolute path to the image file (png, jpg, etc).
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 disclose behavioral traits but only states the action. It doesn't mention overwriting behavior, required permissions, file format/ size limits, or whether the operation is destructive.

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, efficient sentence. It is front-loaded and wastes no words, though it could benefit from additional context.

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, the description lacks behavioral context, preconditions, and error conditions. It is too minimal for a tool with no annotations.

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% with descriptions for both parameters. The description adds minimal meaning beyond the schema (just 'avatar image' context).

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 action 'Upload' and the resource 'avatar image for a voice profile', making it distinct from sibling tools like voicebox_delete_avatar.

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 on when to use this tool vs alternatives (e.g., update_profile), no prerequisites (e.g., profile must exist), and no conditions for use.

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