Skip to main content
Glama
Sign In

Mixer AI

by io.github.y110692
OverviewDiscussionsAdmin

Canvas Private Voices

aimixer_canvas_private_voices
Read-onlyIdempotent

Use when choosing a verified private voice for an owned Canvas project. List active, still-owned voices by name and opaque selector; report whether safe playback is available (no sample audio is retained). No upstream voice IDs. Rechecked again before paid execution.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_id": "<project_id>"
    },
    "name": "aimixer_canvas_private_voices"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNo
project_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent and non-destructive, so the description's extra context is the value: no sample audio retained, selectors are opaque with no upstream voice IDs exposed, and voice ownership is rechecked before paid execution. That is genuine behavioral disclosure beyond the structured fields, though it doesn't explain ordering or result limits.

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?

Four short sentences, front-loaded with the 'Use when' trigger. Minor telegraphic fragments ('No upstream voice IDs') are terse but not padding.

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

Completeness4/5

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

No output schema, and the description does describe the returned fields (name, opaque selector, safe-playback availability). What remains missing is the effect of the lang parameter and any collection size or pagination behavior, but for a two-parameter read-only listing it is largely sufficient.

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

Parameters2/5

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

Schema coverage is 0%, so the description must carry parameter meaning. It hints that project_id must reference an owned project, but never explains the required project_id's format or the optional lang enum (ru/en/es/pt) and whether it filters the listing.

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?

States a specific verb and resource ('list active, still-owned voices' for an owned Canvas project) and adds scope qualifiers (verified private voices, opaque selector). It is distinguishable from the sibling aimixer_voice_manager_list only implicitly, but an agent can tell this is the Canvas-scoped private-voice listing.

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

Usage Guidelines4/5

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

'Use when choosing a verified private voice for an owned Canvas project' gives a clear trigger condition. It does not name the alternative (aimixer_voice_manager_list) or state exclusions, so it falls short of the explicit when/when-not bar.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Mixer AI toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources