Skip to main content
Glama

AvatarSay

Create Fast NPC / Character Voice Line (MP3)

create_npc_voice_line

Synthesize an instant (<3s) English character voice bark or tabletop NPC dialogue MP3 (1–500 chars) in one of 8 preset voices with optional speed and emotion control. Costs 2 credits per 100 characters (minimum 2 credits — a new 30-credit account can generate 15 tabletop MP3 barks free). Returns a 24-hour signed MP3 download URL immediately. Requires Authorization: Bearer avs_...

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": {
      "script": "<script>",
      "voiceId": "<voiceId>"
    },
    "name": "create_npc_voice_line"
  }
}

Input Schema

NameRequiredDescriptionDefault
speedNoOptional speech speed multiplier (0.8–1.2, default 1.0).
scriptYesEnglish spoken dialogue line (1–500 chars).
emotionNoOptional vocal emotion delivery: neutral, happy, angry, sad, fearful, surprised (default "neutral").
voiceIdYesBuilt-in English voice ID: Friendly_Person, Wise_Woman, Lively_Girl, Calm_Woman, Casual_Guy, Deep_Voice_Man, Patient_Man, Young_Knight.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior5/5

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

Annotations only flag the write/open-world/non-idempotent profile; the description adds substantial context beyond them: sub-3s latency, pricing (2 credits per 100 chars, 2-credit minimum, 15 free barks on a 30-credit account), the required Bearer avs_ auth header, and a 24-hour signed URL returned immediately. This is exactly the cost/auth/latency information an agent needs before calling a paid, non-idempotent generator, and it is consistent with the annotations.

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?

Three information-dense sentences with the capability, cost, and return value front-loaded; nothing is redundant. The parenthetical free-tier example (15 barks) is slightly promotional, which keeps it just short of maximally tight.

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?

There is no output schema, yet the description covers the return value (24-hour signed MP3 download URL), latency, cost, and auth, which are the facts an agent needs to sequence and budget the call. For a 4-parameter, no-nested-schema generation tool, nothing material is missing.

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 description coverage is 100%, with both enums (voiceId, emotion) and ranges (script 1-500, speed 0.8-1.2) fully documented in the schema. The description only restates '8 preset voices with optional speed and emotion control' and the 1-500 char limit, adding no syntax, defaults, or trade-offs beyond what the schema already provides, so the baseline 3 applies.

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?

Specific verb + resource + output format: 'Synthesize an instant (<3s) English character voice bark or tabletop NPC dialogue MP3' in one of 8 preset voices. The MP3/voice-line scope is unmistakable and the word 'instant' separates it conceptually from create_talking_video and roll_rpg_npc, but no sibling is named explicitly, so an agent must infer 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 Guidelines3/5

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

Use cases are strongly implied by 'character voice bark or tabletop NPC dialogue' and the free-tier example about 15 tabletop barks. However, there is no explicit when-to-use/when-not-to-use rule and no pointer to alternatives such as create_talking_video for video output or list_voices_and_styles for discovering voices, so the routing decision is left to inference.

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