Skip to main content
Glama
Sign In

Ania

by solutions.diatech
OverviewDiscussionsAdmin

Studio: write the script

studio_escrever_roteiro

Saves an episode’s Ania Script: { titulo, cenas: [{ id, layout, conteudo, falas: [{ id, texto }] }] } (project fields such as apresentadores or marca may be overridden). It is validated with the renderer’s own schema first: on errors NOTHING is saved and the problems come back (in Portuguese) for you to fix and call again; warnings are returned after saving. Layout ids come from studio_listar_layouts. Write calm speech (short sentences), one idea per scene. 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>",
      "roteiro": "<roteiro>"
    },
    "name": "studio_escrever_roteiro"
  }
}

Input Schema

NameRequiredDescriptionDefault
projetoYesProject slug, from studio_listar_projetos.
revisaoNoRevision you read (studio_ver_episodio); refused if it changed since.
roteiroYesThe episode script (Ania Script v1 without schema/projeto).
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

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnly=false, destructive=false, openWorld=false) by disclosing atomic validate-then-save semantics, that errors return in Portuguese with nothing persisted, that warnings are only returned after saving, that project-level fields may be overridden, and that the call is free. These are exactly the behavioral traits an agent needs before mutating state.

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?

Front-loads the payload shape and the failure behavior, with no redundant restatement of the name. The trailing writing-style advice ('short sentences, one idea per scene') is arguably out of scope for invocation but is brief and does not obscure the core content.

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 nested-object write operation with no output schema, the description covers the important contract: validation-then-save atomicity, error/warning delivery, and the top-level script shape. The inner Ania Script v1 schema is only sketched rather than fully specified, so a small gap remains for deeply nested fields.

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, but the description adds real meaning: it enumerates the nested roteiro structure (titulo, cenas with id/layout/conteudo/falas) that the schema only labels generically, and it flags the project-field override behavior. It does not clarify revisao or language beyond the schema text.

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 ('Saves an episode's Ania Script') and immediately shows the payload shape it accepts, so the agent knows exactly what is being written. It also distinguishes itself from the read-side sibling by pointing to studio_listar_layouts for layout ids.

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?

Explains the workflow: validation runs first, on errors nothing is saved and you fix and call again, and layout ids must come from studio_listar_layouts. It lacks an explicit 'do not use this to...' alternative routing, but the context is clear enough for correct selection.

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