Skip to main content
Glama
Sign In

Ania

by solutions.diatech
OverviewDiscussionsAdmin

Studio: render progress

studio_andamento
Read-only

Progress of an episode’s render (latest version, or versao): queued (with position), rendering (%), ready or failed (with why). Also says when the voice fell back to Nanda. Free.

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": {
      "projeto": "<projeto>",
      "episodio": "<episodio>"
    },
    "name": "studio_andamento"
  }
}

Input Schema

NameRequiredDescriptionDefault
versaoNoVersion number (optional).
projetoYesProject slug, from studio_listar_projetos.
episodioYesEpisode number ('01'), ref ('01-visao-geral') or slug.
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

A3.7/5.0
Behavior4/5

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

Annotations already declare a safe, closed-world read, but the description adds real behavioral context: the default is the latest version unless `versao` is supplied, the exact state vocabulary and what each state carries, and the note that a voice fallback to Nanda is surfaced. 'Free' also tells the agent there is no spend risk, which annotations do not cover.

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?

One dense, front-loaded sentence with the version default placed right after the resource, followed by a short cost note. The state list reads as telegraphic but every clause carries information; nothing is padding.

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?

With no output schema, the description usefully enumerates the return states and what each includes, which is exactly what an agent needs to interpret the result. Minor gaps remain — no guidance on polling cadence or what identifies the returned version — but nothing essential to calling it correctly is missing.

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 schema already documents all four parameters. The description only adds one semantic point — that omitting `versao` targets the latest version — which is a modest increment over the schema baseline.

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?

States a specific resource — the render progress of an episode — and enumerates the possible outcomes (queued with position, rendering %, ready, failed with reason). Clear enough to separate from studio_renderizar, but it never names that sibling or any other, so the distinction is inferred rather than stated.

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 implied by 'progress of an episode's render' — an agent can deduce it is a polling/status check — and 'Free' signals no credit cost. There is no explicit when-to-use versus studio_ver_episodio or studio_mostrar_video, and no mention of when not to call it.

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