Skip to main content
Glama
Sign In

Imaginou

by com.imaginou
OverviewDiscussionsAdmin

Approve storyboard → generate videos

approve_storyboard
Destructive

Approves the current six frames, dialogue and claims and queues the three videos. Use acceptFindings=true only when the person explicitly accepts flagged fidelity findings. Fails safely if the storyboard changed since you looked.

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>"
    },
    "name": "approve_storyboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
fingerprintNostoryboardFingerprint you reviewed; defaults to the current one.
productionIdYesProduction ID (from list_productions or create_production).
acceptFindingsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, idempotentHint=false, openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavior: a stale-state fail-safe tied to the fingerprint, and the side effect of queuing three videos on success — important context for a destructive mutation.

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?

Three short sentences, front-loaded with the action and its side effect, then the risky-flag policy, then the failure guarantee. No filler.

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 destructive, non-idempotent approval tool with no output schema, the description covers preconditions, side effects, and the risky flag. What happens on the failure path after 'fails safely' (error shape, whether partial videos are queued) and what success returns are left implicit.

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 67%, and the one undocumented parameter (acceptFindings) is exactly the one the description explains, including a gating policy rather than just a type. The description reinforces the fingerprint's stale-guard purpose. It stops short of full compensation since fingerprint fallback semantics are only in the schema.

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?

Specific verb+resource (approves the storyboard) plus the consequence (queues the three videos), and it names the artifacts covered (six frames, dialogue, claims). An agent can distinguish this from view_storyboard_images and request_storyboard_changes without opening a schema.

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?

Gives an explicit conditional rule for acceptFindings (only when the person explicitly accepts flagged findings) and a precondition behavior ('fails safely if the storyboard changed'). It does not explicitly route the agent away from request_storyboard_changes or review_video, so it falls short of a 5.

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