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.

Generate Fictional Character Avatars

generate_avatars

Generate 2 square (1024×1024) fictional character portraits from a text description in one of 8 art styles. Costs 4 credits (Standard) or 6 credits (HD for accounts that have purchased a pack). Enqueues asynchronously and returns jobId immediately — call get_job after ~5–10 seconds to get the 2 assetIds and signed image URLs. 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": {
      "prompt": "<prompt>",
      "style": "<style>"
    },
    "name": "generate_avatars"
  }
}

Input Schema

NameRequiredDescriptionDefault
styleYesArt style preset ID: anime, 3d-cartoon, pixel-art, realistic, professional-headshot, fantasy, watercolor, cyberpunk.
promptYesVisual description of an original fictional character (3–500 chars), e.g. "weathered dwarven blacksmith with copper braids and glowing forge goggles". Avoid real people, celebrities, or explicit content.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare mutation/open-world/non-idempotent; the description adds substantial operational detail beyond that: credit cost (4 Standard / 6 HD), the Bearer avs_ auth requirement, async enqueue behavior, and the polling delay before results exist. The non-idempotency annotation is consistent with a credit-charging generator, so agents understand repeated calls cost credits.

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?

Four dense sentences, front-loaded with what is produced before cost, auth, and async workflow. Every sentence carries actionable information; no filler or repetition of the title.

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 fully covers the return contract: immediate jobId, then 2 assetIds and signed image URLs via get_job. Auth, cost, timing, and output count are all present, leaving nothing an agent needs to call it correctly unstated.

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% — prompt and style are both fully documented with lengths, an example, and the closed enum. The description restates the 8 styles and output dimensions but adds no new per-parameter semantics. It also references an HD tier that does not appear as a parameter in the schema, which adds slight ambiguity rather than clarity.

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 precise verb and resource — generate 2 fictional character portraits from a text description — plus output format (1024×1024 squares) and the style dimension. It is unmistakable against siblings like list_avatars and get_job, which are read operations.

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?

Explicitly tells the agent the invocation pattern: this enqueues asynchronously and the agent should call get_job after ~5–10 seconds to retrieve results. It also flags the account-tier condition for HD pricing. It does not explicitly exclude alternative generation tools like create_talking_video, so it falls short of a full 5.

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.