Skip to main content
Glama

AvatarSay — Fictional Character, RPG NPC & Talking Video MCP

This connector has been deprecated

Replaced by AvatarSay.

Consolidated into the primary verified AvatarSay connector com.avatarsay/avatar-say.

List Avatar Styles, Voices & Credit Pricing

list_voices_and_styles
Read-onlyIdempotent

Return all 8 AvatarSay visual styles, all 8 built-in English TTS voices (with audio sample URLs), per-action credit costs (including first free 5s talking clip and 2-credit NPC voice lines), and one-time credit pack pricing. Public read-only tool — does not require an API key.

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_and_styles"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's added value is the "does not require an API key" access note and the concrete contents of the response, including the free 5s talking clip and 2-credit NPC voice lines. It does not describe the shape of the returned payload or whether results are cached, which keeps it below a 5.

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?

One front-loaded sentence that packs the enumerated return contents before the access note, with no filler. It is dense to the point of being a run-on, which slightly hurts scanability but wastes no words.

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

Completeness5/5

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

With no parameters, no output schema, and annotations already carrying the safety profile, the description is the only place to learn what comes back — and it enumerates styles, voices with sample URLs, per-action credit costs, and pack pricing. Nothing an agent needs in order to decide to call it is missing.

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 there is no parameter meaning to add; baseline 4 applies. The description correctly does not invent any inputs, reinforcing that this is a no-argument catalog call.

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?

States a specific verb ("Return") plus an enumerated resource set: 8 visual styles, 8 English TTS voices with sample URLs, per-action credit costs, and credit pack pricing. This clearly separates it from siblings like list_avatars (avatars only) and get_credits (balance only) without needing to open either schema.

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?

The description implies usage by naming what is returned (styles, voices, pricing), which suggests calling it before configuring a video or NPC line, but it never says when to use it versus list_avatars or get_credits, nor any when-not condition. The "public read-only, no API key" note is useful context but is not selection guidance.

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.