Skip to main content
Glama

Kleo

by com.kleooai
OverviewDiscussionsAdmin

Storyboard guide (write your own video)

kleo_storyboard_guide
Read-onlyIdempotent

Step 2 (recommended). Returns how to write a storyboard Kleo renders, in the order it should be written: first the DIRECTION of the film (subject, goal, audience, tone, the facts from the request that the narration must still say, the world it is drawn in, what must never appear, and one accent colour per section), then the scene and shot shapes, the limits Kleo enforces before anything is billed, and one worked example. Kleo has two looks, realistic and animation; in both every shot starts as one frame drawn in that look — in the film it becomes a generated clip, in the animatic the camera moves over the frame — so the same storyboard serves both products. Call it once per conversation, before kleo_create_video. Without a storyboard Kleo plans a more generic one from the prompt.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
styleNoThe look: "realistic" (filmed) or "animation" (a 2D animated film); in both every shot is generated footage from its own frame, under the narration. Realistic when omitted.
formatNoThe frame the video will be in. The explainer authors its drawings in the frame's own pixels, so its guide prints different coordinates for 9:16 and 16:9; the template's own format is used when this is omitted.
productNoThe product the user chose (film or animatic): a film's pictures become paid clips, and the guide says how many a line can carry. Film when omitted.
templateNoOptional: Kleo uses the only active workflow, film.
duration_sNoTarget length in seconds, if the user chose one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / product
      Added value: +{
+  "description": "The product the user chose (film or animatic): a film's pictures become paid clips, and the guide says how many a line can carry. Film when omitted.",
+  "enum": [
+    "film",
+    "animatic"
+  ],
+  "type": "string"
+}
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already mark it read-only and idempotent, but the description adds valuable behavioral context: it returns guides, mentions 'limits Kleo enforces before anything is billed,' and clarifies that the same storyboard serves both film and animatic. This goes beyond the structured annotations.

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?

The description is dense but every sentence earns its place. It front-loads the action ('Step 2 (recommended). Returns how to write a storyboard...') and then efficiently covers ordering, product behavior, invocation timing, and fallback behavior without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having no output schema, the description comprehensively explains what the returned guide contains, how it should be used, when to call it, and what happens if it isn't called. Combined with the rich input schema and annotations, nothing essential is missing for an agent to invoke it correctly.

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%, and the schema already gives detailed descriptions for style, format, product, template, and duration_s. The description adds high-level context about the two looks and shared storyboard, but does not materially extend parameter-level meaning beyond 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?

The description clearly states the tool's purpose: it returns how to write a storyboard Kleo renders, in the order it should be written. It distinguishes itself from siblings by specifying it is Step 2 and should be called before kleo_create_video.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit usage context: 'Call it once per conversation, before kleo_create_video.' It also explains the consequence of not using it: 'Without a storyboard Kleo plans a more generic one from the prompt,' which tells the agent when this tool is needed.

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

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