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 Generation Job Status & Download URLs

get_job
Read-onlyIdempotent

Check the status (queued, running, succeeded, failed) of an image or talking-video job (job_...) and return 24-hour signed download URLs once succeeded, or refund details if failed. 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": {
      "jobId": "<jobId>"
    },
    "name": "get_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYesJob ID (job_...) returned by generate_avatars or create_talking_video.

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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is known. The description adds genuinely new behavior: the required 'Authorization: Bearer avs_' header, the 24-hour expiry on signed download URLs, and that failed jobs return refund details — none of which the annotations convey. It does not describe the response envelope or whether repeated calls on a finished job are cheap, so it is not exhaustive.

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 dense sentences with no filler: the status enumeration and outcome contract come first, then the auth requirement. Every clause carries information an agent needs before calling.

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

Completeness4/5

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

For a single-parameter polling tool with no output schema, the description covers the state space, success outputs (signed URLs), failure outputs (refund details), and auth. What is missing is polling guidance (retry interval, whether running jobs should be re-polled) and any sense of the response object's shape beyond the highlighted fields.

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?

There is a single required parameter with 100% schema description coverage, so the schema already explains that jobId is a 'job_...' value returned by generate_avatars or create_talking_video. The description only repeats the 'job_...' prefix, adding no new meaning such as format constraints or what happens with an expired/unknown ID; baseline 3 applies.

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 and resource: 'Check the status ... of an image or talking-video job (job_...)', and enumerates the possible states (queued, running, succeeded, failed). The job_ prefix plus the reference to jobs returned by generate_avatars/create_talking_video cleanly separates it from the creation siblings without needing to open any schema.

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?

The description makes the usage context clear: it is the follow-up call for a job created by generate_avatars or create_talking_video, and it returns usable URLs only once succeeded. It gives no explicit exclusions or polling cadence (how often to re-check a running job), so it stops short of full when/when-not 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.