Skip to main content
Glama
Sign In

Ania

by solutions.diatech
OverviewDiscussionsAdmin

Creation status

creation_status
Read-only

Where an avatar creation stands: status, what awaits review and the previews (image and movements) to show the user. Without jobId, lists recent creations ("continue my avatar"). Free. Generation takes minutes: do not poll in a loop; the user gets an email when there is something to review.

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

Input Schema

NameRequiredDescriptionDefault
jobIdNoThe job id from criar_avatar or ver_andamento.
languageNoThe 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.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly/non-destructive/closed-world, and the description adds genuinely new behavioral facts: the call is free, generation latency is minutes, the user is notified by email, and polling loops are discouraged. It also discloses what the response contains (status, review queue, previews), which is the main behavioral gap for a status tool.

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?

Three tight sentences: what it returns first, then the no-jobId mode, then the cost/latency/polling constraint. Every sentence carries operational information with no filler or repetition of the schema.

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 must carry the return-shape burden, and it does by naming status, pending-review items, and previews. Combined with the polling and notification guidance, an agent has everything needed to call this correctly in either mode.

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 baseline is 3; the description earns above that by explaining the semantic effect of omitting the optional jobId — it switches the tool into a recent-creations listing mode. It adds nothing about the language parameter beyond the schema, which keeps it from a 5.

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 resource and verb-of-state: where an avatar creation stands, plus exactly what is returned (status, what awaits review, previews for image and movements). It also distinguishes its two modes — single job lookup with jobId versus a recent-creations list without it — so an agent can tell it apart from list-style siblings such as my_avatars.

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?

Gives clear usage context ('continue my avatar' when jobId is omitted) and an explicit anti-pattern ('do not poll in a loop') plus the reason (generation takes minutes, email notification arrives). It stops short of naming sibling alternatives (e.g., my_avatars, get_avatar) or when this is the wrong tool, so it is strong but not exhaustive routing guidance.

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

All Ania toolsInspect
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