Skip to main content
Glama
Sign In

Ania

by solutions.diatech
OverviewDiscussionsAdmin

Studio: download the video

studio_baixar
Read-only

Signed download links (valid ~15 min) for a finished episode video: MP4 1080p and the 720p copy for phones. Free. The video is the user’s.

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_baixar"
  }
}

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?

The annotations already declare this is a non-destructive, closed-world read, so the description's job is lighter. It still adds real behavioral context beyond the schema: links are signed, expire in ~15 minutes, downloads are free, and the video belongs to the user. It does not state whether requesting a download triggers a render or what happens if the version is unavailable.

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?

Two tight sentences with the key fact (signed, ~15 min expiry) front-loaded and zero redundant wording. The clipped fragments ("Free. The video is the user's.") are efficient but read slightly telegraphic rather than fully structured.

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 read-only tool with full schema coverage and no output schema, the description covers what matters: the return is signed URLs with a limited lifetime and two resolutions. The one missing piece is routing to the sibling an agent should call when the episode is not yet finished.

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%, with projeto, episodio, versao, and language all documented in the schema, so the baseline of 3 applies. The description adds no parameter-level meaning beyond what the schema already states.

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?

The description names a specific verb+resource (signed download links for a finished episode video) and specifies the deliverables: MP4 1080p plus a 720p phone copy. It is clear what the tool does, but it never distinguishes itself from siblings like studio_renderizar or studio_mostrar_video, which an agent could easily confuse with it.

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?

"For a finished episode video" implies the prerequisite that a render must already exist, which is useful context. However, there is no explicit when-to-use vs. when-to-use-something-else guidance, and no named alternative for the case where the episode is not yet rendered.

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