Ania

Show my avatar

show_my_avatar

Read-only

Shows one of the user’s avatars ALIVE in the chat: animated, waving and saying a lip-synced welcome line (visual card in ChatGPT and Claude). Use when an avatar is ready or the user asks to see one of theirs. Free. In apps without cards, the reply carries the thumbnail and movements as text.

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": {
      "avatarId": "<avatarId>"
    },
    "name": "show_my_avatar"
  }
}

Input Schema

Name	Required	Description
`say`	No	Optional welcome line.
`avatarId`	Yes	Avatar id from meus_avatares or a finished job.
`language`	No	The user's language as a BCP-47 tag (e.g. 'en', 'en-US', 'pt-BR', 'es'). Replies and prices follow it.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already establish readOnly/closed-world/non-destructive, and the description adds real value beyond them: it discloses that the output is an animated visual card in ChatGPT and Claude, that it is free, and that apps without card support fall back to a text rendition with thumbnail and movements. Missing are any error or failure conditions (e.g., what happens with an invalid or unfinished avatar id).

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 sentences, front-loaded with the core behavior and then the trigger, cost, and fallback rendering. Slightly dense with parenthetical and capitalized emphasis, but no sentence is wasted.

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 three-parameter, no-output-schema tool, the definition covers what is produced in both card and non-card environments plus the pricing note, which is enough to call it correctly. The one substantive omission is the relationship to the similarly named sibling 'show_avatar'.

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%, so the three parameters are already documented in the schema, including the BCP-47 language tag and the avatar id source. The description only indirectly gestures at the optional welcome line ('saying a lip-synced welcome line') and adds no syntax or format detail beyond the schema; 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?

The description gives a specific verb and resource ('Shows one of the user's avatars') and richly qualifies the result: animated, waving, lip-synced welcome line, rendered as a visual card. It does not, however, distinguish this from the sibling 'show_avatar', which an agent could easily confuse with it.

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?

It states the trigger conditions clearly ('when an avatar is ready or the user asks to see one of theirs'), which is actionable context. It offers no exclusions or explicit alternative, so the sibling 'show_avatar' remains unaddressed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Ania tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?