shapeless

List actors

characters_list

Read-only

List account actors with voice descriptions and locked parts to reuse an existing voice before designing a new one. Requires read scope.

Instructions

The account's actors: who they are, what their voice is, and which parts are locked. voiceDescription is the casting direction a designed voice was written from - read it before designing another one, and reuse the actor that already fits. Needs the read scope.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`characters`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.4Oct 13, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered; the description adds the auth requirement ('Needs the read scope') and flags which attributes are meaningful (voice direction, locked parts). That is real context beyond the structured fields, though there is no detail on result size or ordering.

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?

Two compact sentences, front-loaded with what the resource is and then the workflow instruction. Every clause earns its place, though the em-dash sub-clause about `voiceDescription` makes the second sentence fairly dense.

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?

An output schema exists, so return shape need not be restated, and the description supplies the remaining essentials: the read scope requirement and the key field to inspect. For a parameterless read tool this is close to complete, with only minor gaps around ordering or pagination.

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

Parameters4/5

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

The tool takes zero parameters, so the schema cannot carry semantic weight and the baseline is 4. The description correctly implies a whole-account listing with no filtering argument, matching the empty input schema.

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 (list) and resource (the account's actors) and enumerates what each entry carries: identity, voice, and locked parts. It also names a concrete field (`voiceDescription`) the agent will encounter, which goes beyond a generic 'list actors' label. It doesn't explicitly disambiguate from the sibling `characters_voice`, though the nearby mention of 'designing another' voice implies the distinction.

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?

Gives actionable when-to-use guidance: read `voiceDescription` before designing another voice and reuse the actor that already fits, which frames this as the lookup step preceding a voice-design action. It also states the prerequisite ('Needs the read scope'). No explicit when-not or named alternative tool, so it stops short of 5.

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

Deploy Server