Skip to main content
Glama
Sign In

Imaginou

by com.imaginou
OverviewDiscussionsAdmin

Approve or reject the generated video

review_video
Destructive

For quality_hold or awaiting_final_review: approve after the person watched the video (moves on to music or completion), or reject to return to the storyboard for changes.

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": {
      "productionId": "<productionId>",
      "decision": "<decision>"
    },
    "name": "review_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
decisionYes
productionIdYesProduction ID (from list_productions or create_production).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructive/non-idempotent/not-read-only. Beyond that, the description adds meaningful lifecycle effects: approve moves to music or completion, reject returns to the storyboard for changes. It does not mention error behavior for invalid states or reversibility, but it provides useful workflow context.

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?

A single front-loaded sentence with zero waste. The state precondition comes first and each clause earns its place by adding state, action, or consequence.

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 two-parameter state-transition tool with no output schema, the description covers valid starting states and both outcome paths. It could say more about failure modes or what the caller receives, but the core decision context is complete.

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 only 50%, but the description compensates by explaining the real meaning of the decision enum: 'approve' advances the workflow and 'reject' sends the video back to storyboard. productionId is documented in the schema.

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 states a specific pair of verbs (approve/reject) applied to the generated video, and the workflow consequences distinguish it from storyboard-approval siblings. It does not explicitly name sibling tools, but the resource and action are clear.

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?

It explicitly limits use to quality_hold or awaiting_final_review and explains the conditions for each decision: approve after the person watched the video, reject to return to the storyboard. Alternatives are implied by the workflow rather than named explicitly.

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

All Imaginou 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