Skip to main content
Glama

list_voices

Retrieve the voices saved in your Miragea account and return their IDs for use as voice_id in text-to-speech requests.

Instructions

List voices saved in the user's Miragea account (ids to pass as voice_id).

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": "list_voices"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It discloses the important scoping fact that results are limited to the user's own account and the 'List' verb implies a safe read, but it says nothing about pagination behavior, ordering, or what happens when limit/offset exceed the result set.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with the resource and scope front-loaded and the practical payoff in a tight parenthetical. There is no filler and nothing is buried.

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?

For a simple two-parameter list tool with no output schema and no annotations, the description covers what the tool returns conceptually (voice ids) and the account scope. It is still thin on result shape and paging, which the agent must infer from default limit/offset values alone.

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 the two parameters (limit and offset), and the description adds no semantics for either. The only added value is naming the return identifier (voice_id), which is not a parameter concern, so the required compensation for the undocumented schema is absent.

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 states a specific verb and resource ('List voices') and scopes it to the user's Miragea account, then clarifies the downstream purpose ('ids to pass as voice_id'). It is clearly distinguishable from siblings like speak and transcribe, though it never explicitly names an alternative.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the parenthetical tells the agent this is how you obtain a voice_id for another call, which is a meaningful hint. There is no explicit when-to-use/when-not framing, no mention of the sibling speak tool by name, and no guidance on paging through results.

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