Skip to main content
Glama

use_style

Destructive

Switch the project to a built-in or saved art style and rebuild every shot’s characters, objects, and places while keeping words, cameras, and timing unchanged.

Instructions

Switch the project to another art style, a built-in id (list_styles) or one of the person's own (my_styles). Every shot is rebuilt in the new style: its characters, objects and places are replaced; words, cameras and timing stay. One undo step, and no confirm step, so ask the person first if the project has work. A style built since Dinoctor opened makes the window reload once. For built-in styles with a confirm step, set_style does the same.

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": {
      "id": "<id>"
    },
    "name": "use_style"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesA style id from list_styles or my_styles.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.2
    • addedInput schema / properties / id / description
      Added value: +"A style id from list_styles or my_styles."
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the destructiveHint=true annotation by specifying exactly what is destroyed (characters, objects, places are replaced) and what survives (words, cameras, timing). It also discloses the single undo step, the absence of a confirmation prompt, and the one-time window reload for newly built styles — all behavior an agent must know before calling.

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?

Front-loads the action and id sources, then layers consequence, safety, and edge cases in short sentences with zero filler. Every sentence carries information an agent needs before invoking a destructive switch.

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 destructive single-parameter tool with no output schema, the description covers consequences, reversibility, confirmation behavior, reload side effects, and the sibling alternative. Nothing material for a correct call is missing.

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?

Only one parameter and schema coverage is 100%, with the schema itself already saying 'A style id from list_styles or my_styles.' The description restates that same fact, so it adds little new meaning beyond the schema; baseline 3 applies.

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?

States a specific verb and resource ('Switch the project to another art style') and immediately names where ids come from (list_styles, my_styles), plus distinguishes itself from set_style. An agent can tell this apart from the sibling style tools 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 Guidelines4/5

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

Gives real usage context: 'no confirm step, so ask the person first if the project has work,' and routes agents to set_style when a confirm step is wanted for built-in styles. The alternative routing is implied rather than stated as a hard rule, which keeps it just 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.