Skip to main content
Glama

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

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: only active, still-owned voices are returned, selectors are opaque with no upstream voice IDs exposed, no sample audio is retained, and ownership is re-verified before paid execution. That last point is a meaningful consistency guarantee an agent would not otherwise know.

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, then output shape, then constraints. Dense but each clause carries information; some phrasing ('opaque selector', 'no upstream voice IDs') is terse to the point of needing interpretation.

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?

Output schema exists, so return values need no prose, and the annotations plus description cover the safety and freshness story well. What is missing is any explanation of how project_id and especially the lang filter affect the result set, which is the one thing an agent must get right to call this correctly.

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 description coverage is 0% for both parameters, so the description carries the full burden and fails to do so. Neither 'project_id' (the required scope) nor 'lang' (an ru/en/es/pt filter, presumably restricting returned voices by language) is mentioned or explained; the enum values in the schema tell an agent nothing about whether lang filters results or affects the selector.

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?

Uses a specific verb and resource ('List ... voices') scoped to 'an owned Canvas project', plus the qualifying adjectives 'active, still-owned'. It is clearly a read-only enumeration of selectable voices, distinct from siblings like aimixer_canvas_find_models or aimixer_canvas_list, though it never names an alternative directly.

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 an explicit trigger condition, and 'Rechecked again before paid execution' implies the tool belongs upstream of an execution step. It stops short of naming a sibling alternative or stating exclusions (e.g. what to use for upstream/library voices).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources