Kuro

Add a note to a film

add_storyboard_note

Put a sticky note on a film's canvas, optionally near a scene and in a color. The brief prints it with the [id] update_storyboard_annotation and remove_storyboard_annotation take. One undo step; undo_storyboard takes it back. Spends no credits.

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": {
      "storyboard_id": "<storyboard_id>",
      "text": "<text>"
    },
    "name": "add_storyboard_note"
  }
}

Input Schema

Name	Required	Description	Default
`text`	Yes
`color`	No
`near_scene`	No
`storyboard_id`	Yes

Output Schema

Name	Required	Description	Default
`cast`	Yes
`brief`	Yes
`notes`	Yes
`quote`	No
`texts`	Yes
`scenes`	Yes
`sounds`	Yes
`videos`	Yes
`credits`	Yes
`history`	Yes
`message`	Yes
`skipped`	No
`started`	No
`stopped`	No
`accepted`	No
`receipts`	No
`schedule`	Yes
`settings`	Yes
`reference`	No
`storyboard`	Yes
`download_url`	No
`generation_id`	No
`remaining_scenes`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 26, 2026

TDQS

A4/5.0

Behavior4/5

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

Adds real traits beyond annotations: one undo step, reversible via undo_storyboard, and zero credit cost — none of which are in the structured fields. Non-idempotency is declared in annotations but not reinforced here, and the description never states whether the note is immediately visible to collaborators.

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 tight sentences, front-loaded with the action, then the id/update linkage, then undo and cost. No filler and no repetition of schema or annotation data.

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?

An output schema exists so return values need no explanation, and the description still flags the returned id's purpose. Missing only a note on text length limits and required storyboard_id, which matters given 0% schema description coverage.

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 0%, so the description carries the load. It conveys the intent of near_scene and color ('optionally near a scene and in a color') but says nothing about the 280-character text cap or that storyboard_id is a required UUID, leaving two of four params unelaborated.

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?

Specific verb and resource: 'put a sticky note on a film's canvas' clearly distinguishes a freeform annotation from the sibling text/sound additions. It stops short of explicitly contrasting with add_storyboard_text, which an agent might otherwise confuse with a note.

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?

Names the follow-on tools (update_storyboard_annotation, remove_storyboard_annotation) and explains the id linkage, plus points to undo_storyboard for reversal. It gives clear post-create routing but no guidance on when to choose this over add_storyboard_text or set_brand_note.

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

All Kuro tools Inspect

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

Need Help?