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.

Get Account Credit Balance

get_credits
Read-onlyIdempotent

Return the authenticated AvatarSay account email, current non-expiring credit balance, image quality tier (standard vs hd), whether the 0-credit first talking video clip is still available, and how many avatar generations, NPC voice lines, or video seconds the balance covers. Requires Authorization: Bearer avs_...

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the description does not need to re-litigate safety. It adds genuinely new behavioral context: the explicit auth requirement (Authorization: Bearer avs_...) and the fact that credits are non-expiring, which an agent would not learn from 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no filler: the purpose and full return contract are front-loaded, and the auth prerequisite is a short closing sentence. The long enumeration earns its length because there is no output schema to document the return shape elsewhere.

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 output schema, the description carries the full burden of describing return values, and it does so field by field, including the '0-credit first talking video clip' availability flag and the balance-to-units conversion. Auth and safety are covered by the text plus annotations, leaving no material gap for a zero-parameter read tool.

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 baseline is 4 and there is nothing for the description to disambiguate at the input level. Nothing in the text misleads about inputs.

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?

The description opens with a specific verb and clearly scoped resource ('Return the authenticated AvatarSay account email, current non-expiring credit balance...') and enumerates every returned field, so an agent can tell this is an account-level balance/entitlement read and not a listing or generation tool like list_avatars or create_talking_video.

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?

Usage is only implied: an agent can reasonably infer this is a pre-flight check before calling create_talking_video or generate_avatars, since the description explains how many generations/voice lines/video seconds the balance covers. It never states when to call it, when not to, or names an alternative, so it sits at the minimum-viable level.

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.