Skip to main content
Glama
Sign In
@vocea.app/mcp-server

@vocea.app/mcp-server

Official
by vocea-admin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

vocea_list_voices

Retrieve a paginated list of cloned voices associated with your Vocea account. Use page and limit parameters to control results.

Instructions

List the authenticated user's cloned voices.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "vocea_list_voices"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default 1)
limitNoResults per page (default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations provided; description relies solely on 'List' implying read-only, but lacks details on authentication, rate limits, pagination behavior, or response format.

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?

Single sentence is concise and front-loaded. Efficient but could benefit from structured sections (e.g., auth info).

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?

Absence of output schema and lack of details about return structure (e.g., array of voice objects) leaves the agent guessing about response format and fields.

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 page and limit. Description adds no extra meaning to parameters beyond what schema already provides.

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?

Description uses specific verb 'List' and resource 'cloned voices'. It clearly distinguishes from sibling 'vocea_list_public_voices' by specifying 'authenticated user's cloned voices'.

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 versus alternatives like list_public_voices or when to apply pagination. The description is purely functional.

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

Deploy Server

Other Tools