Skip to main content
Glama

draw_object

Create custom simple objects in the current style's format, then add them to the library or a shot when the style lacks the object you need.

Instructions

Draw a new object yourself, free, in the current style's format, and add it to the person's library and into a shot. Use it for simple objects the style doesn't have; for a photo-like picture use generate_picture (paid). No Claude usage or credits are spent: you send the drawing as plain data and Dinoctor checks it (bad fields are dropped; a drawing that fails is refused with the reason). Call describe_drawing first for the exact format. Formats in short: Pixel = {"name","rows":["..##..",...],"colors":{"#":"#535353"}} (up to 28x28, '.' empty); Toon = {"name","w","h","shapes":[{"type":"rect|ellipse|poly","x","y","w","h","color","points"}]} (y up is negative, stands on y 0); Voxel = {"name","boxes":[{"at":[x,y,z],"size":[w,h,d],"color"}]}; other styles have their own format (describe_drawing). Places in every style: {"name","sky","horizon","floor","dark","stars","clouds","orb","items":[{"kind","x","z","size"}]}. Returns the new id. Then use look to check it.

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

Input Schema

NameRequiredDescriptionDefault
xNoLeft to right, about -6 to 6. Empty spaces it automatically.
shotNoShot index from 0 in that scene.
sizeNo1 is normal.
sceneNoScene index from 0. With no shotId/scene, the shot on screen is used.
shotIdNoThe shot's id (from get_project).
drawingYesONE drawing object in the style's format (not an array).
addToShotNofalse only saves it to the library. Default true: it joins the shot's cast.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare non-read-only, non-destructive, non-idempotent, closed-world behavior, so the mutation profile is covered structurally. The description adds genuinely useful context beyond them: no credits are spent, malformed fields are silently dropped while a fully invalid drawing is refused with a reason, and the new id is returned with a recommended 'look' follow-up. However it says nothing about permissions, whether an existing object is replaced, or limits on placement parameters, so it is good but not exhaustive.

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?

Purpose and the paid alternative are front-loaded in the first two sentences, with formats and mechanics after. It is dense for its length and repeats the describe_drawing pointer twice ('Call describe_drawing first' and 'other styles have their own format (describe_drawing)'), a small redundancy, but nearly every clause carries actionable information.

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?

For a 7-parameter mutation tool with a nested free-form object and no output schema, the description covers the essentials: format examples for three styles, the fallback to describe_drawing, validation behavior, the return value, and a verification step. Remaining gaps are minor, such as the semantics of x/z/size placement and what happens to an object already occupying the spot.

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%, which sets the baseline at 3, and the description's format walkthroughs largely restate what describe_drawing is supposed to supply. It does add the meaningful distinction that exactly ONE drawing object is passed (not an array) and what the place object contains, which is more than the schema conveys, but the heavy format detail is deliberately deferred to a sibling tool.

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 first sentence states a specific verb and resource ('Draw a new object yourself'), plus scope ('in the current style's format') and side effects ('add it to the person's library and into a shot'). It explicitly demarcates itself from the sibling generate_picture, so an agent can route between them without opening schemas.

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?

Gives explicit when-to-use ('simple objects the style doesn't have'), an explicit alternative with its cost tradeoff ('for a photo-like picture use generate_picture (paid)'), and a prerequisite workflow step ('Call describe_drawing first for the exact format'). Very little 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.