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.

Import Stylized Fictional Character Illustration

import_character_portrait

Import an existing non-photorealistic fictional character illustration (anime, 2D/3D cartoon, pixel art, fantasy digital painting, VTT token art; PNG/JPG/WebP, 256–4096 px, max 5 MB) from an https:// URL or base64 data URI for 0 credits, returning an assetId (ast_...) ready for create_talking_video. Camera photographs and photorealistic human likenesses are strictly blocked by EXIF and automated vision screening. Requires confirmFictional=true and 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": {
      "confirmFictional": "<confirmFictional>"
    },
    "name": "import_character_portrait"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelNoOptional character name or short description (up to 160 chars), e.g. "Bramwell Copperbraid — Dwarven Runesmith".
imageUrlNoPublic https:// URL of a PNG, JPG, or WebP stylized character illustration (max 5 MB). Provide either imageUrl or imageBase64.
imageBase64NoBase64-encoded PNG, JPG, or WebP character illustration (raw base64 or data:image/...;base64,... URI, max 5 MB). Provide either imageUrl or imageBase64.
confirmFictionalYesMust be true: confirms this image is a fictional, stylized character illustration and NOT a photograph or likeness of a real person.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only flag openWorldHint and non-idempotency; the description adds substantial behavior beyond that: zero credit cost, the screening mechanism (EXIF plus automated vision screening), the returned assetId prefix (ast_), and the auth prerequisite (Bearer avs_... plus confirmFictional=true). It never contradicts the readOnlyHint=false annotation, since importing creates a new asset.

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?

Front-loaded with purpose in the opening clause, then constraints, cost, and return value in descending priority. It is a single dense sentence-loaded paragraph rather than discrete sentences, which slightly hurts scanability, but no clause is filler.

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?

No output schema exists, so the description carries return-value burden and does so (assetId ast_...) and ties it to the next step. Cost, auth, format/size limits, and the rejection policy are all present, leaving nothing an agent needs before calling it.

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?

Schema coverage is 100%, so the schema already documents all four parameters; the description nonetheless adds a constraint absent from the schema property text, the 256–4096 px dimension range, and reinforces that confirmFictional is mandatory. That is a modest but real increment above the baseline.

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?

Names a specific verb (import) and a tightly scoped resource (an existing non-photorealistic fictional character illustration) and enumerates the accepted art styles and formats. It also names the downstream consumer, create_talking_video, which makes it distinguishable from the generate/list siblings at a glance.

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?

States clear when-to-use context (bring an existing stylized illustration in, zero credits, output feeds create_talking_video) and an explicit when-not (camera photographs and photorealistic likenesses are blocked). It stops short of pointing an agent to an alternative tool for photorealistic or generative needs, so the alternatives half of the bar is unmet.

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.