Ania

Quote an avatar

quote_avatar

Read-only

Prices an animated talking avatar before anything is spent: AI cost + Ania fee (+ own-image preparation, if any), returning a quoteId valid for ~10 minutes. Charges nothing. Use after agreeing the description, style and states (from list_styles) with the user. Show the price and wait for the user’s explicit go-ahead; never confirm for them.

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": {
      "description": "<description>",
      "style": "<style>",
      "states": "<states>"
    },
    "name": "quote_avatar"
  }
}

Input Schema

Name	Required	Description
`style`	Yes	A style id from ver_estilos.
`states`	Yes	2–12 state ids.
`language`	No	The user's language as a BCP-47 tag (e.g. 'en', 'en-US', 'pt-BR', 'es'). Replies and prices follow it.
`description`	Yes	The character, in plain words.
`ownImageRef`	No	Optional, from usar_minha_imagem; the price then includes the prep fee.
`imageQuality`	No	Optional, from ver_estilos.
`videoResolution`	No	Optional, from ver_estilos.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations declare readOnlyHint=true and destructiveHint=false, and the description reinforces this behaviorally ('Charges nothing'), adding a fact annotations cannot express. It also discloses the quote TTL of ~10 minutes, which is critical because a stale quoteId changes downstream behavior. That is real behavioral context beyond the structured fields.

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?

Front-loads the definition and the no-charge guarantee, then the preconditions, then the approval rule. Dense but every clause carries information an agent needs; nothing is decorative.

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 7-parameter read-only pricing tool with no output schema, the description covers purpose, cost model, quote lifetime, and human approval. The only gap is not describing what the returned quote object contains or explicitly naming the follow-up spend step, though the 'never confirm for them' line implies 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 description coverage is 100%, so the schema already documents style, states, language, ownImageRef and the optional quality/resolution fields. The description's added value is modest but real: it frames which parameters must be agreed with the user beforehand and clarifies that own-image preparation only affects price when present, which helps the agent reason about the optional fields rather than just read them.

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 ('Prices an animated talking avatar'), the exact composition of the price (AI cost + Ania fee + optional own-image prep), and the no-charge guarantee. An agent can tell this apart from create_avatar or confirm_spend without opening 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit sequencing ('Use after agreeing the description, style and states (from list_styles) with the user'), names the prerequisite tool, and states the human-in-the-loop rule ('wait for the user's explicit go-ahead; never confirm for them'). Both when-to-use and how-to-proceed are covered.

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?