Skip to main content
Glama

make_style

Create a new art style from words or example images by planning the look, drawing assets, writing the style, testing it, and rendering sample pictures.

Instructions

Start building a brand-new art style from words and/or example pictures, the same as Dinoctor's "Build your own style". Claude Code runs inside Dinoctor on this computer and builds the style in code: it plans the look, draws characters, objects and places, writes the style, runs the app's tests, checks a test shot and makes the pictures. Usually about 30 minutes (longer for a detailed 3D style), and it uses a lot of the person's own Claude usage (a smaller plan can hit its limit). Nothing is paid to Dinoctor. The person can keep working, and cancel_style stops it at any time. Without confirm: true it only says what will happen; ask the person, then call again with confirm: true. Only one style job runs at a time. Then follow it with style_status. To fix a style that exists use fix_style; to resume a stopped build use continue_style.

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe style's name, up to 30 characters.
filesNoFull paths of pictures or short videos on this computer that show the look (up to 25 MB each). They show Claude far more than words.
wordsNoThe look: characters, world, mood, lettering. Needed unless files are sent.
confirmNotrue starts it (uses the person's Claude usage). Only after the person said yes.
useProjectFilesNoAlso send the files already added in Dinoctor's Build your own box.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations it discloses that the job runs roughly 30 minutes, consumes the person's own Claude usage and can exhaust a smaller plan, costs nothing to Dinoctor, can be stopped with cancel_style, permits the person to keep working, and that only one style job runs at a time. It also reveals that omitting confirm makes it a no-op preview — a crucial behavioral trait the readOnly/destructive hints do not capture.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The critical actions (start, confirm gate, cancel, follow with style_status) are front-loaded, and the long-running/cost warning is placed early. A single dense paragraph makes it slightly harder to scan, and the reference to Dinoctor's 'Build your own style' plus the 3D parenthetical are mildly expendable.

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 long-running, usage-consuming creation job with no output schema, the description covers duration, cost, cancellation, concurrency limits, the confirmation prerequisite, and the natural next tool. An agent has everything needed to call it safely and correctly.

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?

With 100% schema coverage the baseline is 3, and the description adds real meaning: it explains that confirm is the actual execution gate ('Without confirm: true it only says what will happen'), that words are 'needed unless files are sent' (a mutual requirement the schema only hints at), and that files show Claude far more than words. It does not elaborate on useProjectFiles 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?

It states a specific verb and resource — 'Start building a brand-new art style from words and/or example pictures' — and explicitly differentiates from siblings by naming fix_style for existing styles and continue_style for resuming stopped builds. An agent can identify this as the creation entry point without inspecting the 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?

It gives explicit when-to-use and when-not-to-use routing (use fix_style for an existing style, continue_style to resume), a mandatory two-step confirm protocol ('ask the person, then call again with confirm: true'), and the required follow-up with style_status. Nothing about sequence is left to inference.

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