Skip to main content
Glama

set_style

Destructive

Switch an entire project to a different built-in art style, rebuilding every shot with the new style's place, light and lead character while keeping texts and lengths. Confirms first if work exists.

Instructions

Switch the whole project to another built-in art style. Every shot is rebuilt from the new style's own place, light and lead character: actions, cast, scenery and keyframes go; texts and lengths stay. If the project already has work, the first call returns needsConfirm; ask, then call with confirm: true. One undo step for the person. For one of the person's own styles use use_style; to start fresh use new_project.

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": {
      "style": "<style>"
    },
    "name": "set_style"
  }
}

Input Schema

NameRequiredDescriptionDefault
styleYesStyle id from list_styles.
confirmNotrue only after the person agreed to rebuild the shots.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.2
    • addedInput schema / properties / confirm / description
      Added value: +"true only after the person agreed to rebuild the shots."
    • changedInput schema / properties / style / description
      Previous value: -"Style id (list_styles)."New value: +"Style id from list_styles."
  2. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, and the description goes well beyond that by specifying exactly what is destroyed (actions, cast, scenery, keyframes) versus what survives (texts and lengths), plus the needsConfirm gate and the single undo step. This is the precise consequence data an agent needs before 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?

Four short sentences, front-loaded with the primary action, then consequences, then the confirmation protocol, then sibling routing. Telegraphic phrasing ('actions, cast, scenery and keyframes go') carries maximum information with no filler.

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?

For a two-parameter destructive mutation with no output schema, the definition covers consequences, reversibility (one undo step), the confirmation round-trip, and alternatives. Nothing an agent needs in order to call it safely is missing.

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 100%, so the baseline is 3, but the description adds real meaning to confirm by tying it to the needsConfirm response and to the person's agreement. It also constrains style to built-in style ids, which the schema's 'Style id from list_styles' only partly conveys.

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+scope: "Switch the whole project to another built-in art style." It immediately distinguishes itself from the sibling use_style (the person's own styles) and new_project (start fresh), so an agent can route correctly without opening any schema.

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?

Explicitly names both alternatives and the condition that selects them: use_style for the person's own styles, new_project to start fresh. It also gives the conditional flow for existing work (ask, then call with confirm: true), leaving nothing to inference.

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