Skip to main content
Glama
Sign In

Ania

by solutions.diatech
OverviewDiscussionsAdmin

Studio: new episode

studio_novo_episodio

Adds the next episode to a project. With de (another episode) it continues the series: same scenes, layouts and rhythm, marked as derived; without it, a one-scene starter. Then write it with studio_escrever_roteiro. 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>",
      "slug": "<slug>"
    },
    "name": "studio_novo_episodio"
  }
}

Input Schema

NameRequiredDescriptionDefault
deNoEpisode to continue from (number, ref or slug). Optional.
slugYesEpisode slug, kebab-case (e.g. 'pricing').
tituloNoEpisode title.
projetoYesProject slug, from studio_listar_projetos.
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.3/5.0
Behavior4/5

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

Annotations only declare a non-destructive mutation; the description adds substantive behavior: derived episodes copy scenes, layouts and rhythm, an empty `de` yields a one-scene starter, and the call is free. It still doesn't say what is returned (episode id/slug) or whether the parent project must exist, which matters since there is no output schema.

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-loaded with the verb and resource, then the mode split, then the next step, then cost — no wasted sentences. The telegraphic fragments ('marked as derived', 'Free.') are efficient but leave a small amount of inference.

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 5-parameter creation tool with full schema coverage and no output schema, the description covers creation semantics, the derived-copy behavior, and the required next step. The remaining gap is the return value and any precondition on the target project.

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 already 100%, so the baseline is 3, but the description genuinely adds meaning to `de` by describing its effect on the created episode rather than just its format. Other parameters (slug, titulo, projeto, language) get no extra explanation, which keeps it below 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 verb and resource ('Adds the next episode to a project') and immediately splits it into two concrete modes, so the agent knows exactly what the tool produces. It also names the follow-up tool, making it distinguishable from siblings like studio_escrever_roteiro.

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?

Clearly says when to pass `de` (continue a series) versus omitting it (one-scene starter), and routes the agent onward with 'Then write it with studio_escrever_roteiro'. No explicit exclusions relative to other siblings, but the two-mode split is a strong usage cue.

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