Skip to main content
Glama

draw_place

Draw a custom place in the current style's format to add it to the library or set it as the shot's place, without spending credits on paid generation.

Instructions

Draw a new place yourself, free, in the current style's format, and add it to the person's library and set it as the shot's place. Use it for simple places the style doesn't have; for a photo-like picture use generate_place (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 = a place object; 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_place"
  }
}

Input Schema

NameRequiredDescriptionDefault
shotNoShot index from 0 in that scene.
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 becomes the shot's place.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 only declare the generic mutation profile, but the description adds real behavioral context: no credits are spent, the drawing is validated server-side with bad fields dropped and failures refused with a reason, the new id is returned, and the place is set as the shot's place by default. That is well beyond what the annotations convey.

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?

Front-loaded with purpose and the paid alternative, then format details. It is dense and the inline format examples make it long, but each sentence carries actionable information; minor tightening of the format block would help.

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 nested-object mutation tool with no output schema, the description covers validation behavior, return value ('Returns the new id'), and a follow-up verification step ('use look to check it'). An agent has everything needed to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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 goes further by spelling out concrete drawing formats per style (Pixel rows/colors, Toon, Voxel boxes, common place fields) and clarifying the addToShot default and the shot/scene fallback. This meaningfully extends the schema's bare 'object' typing.

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 ('Draw a new place yourself') and immediately scopes it against the sibling generate_place ('for a photo-like picture use generate_place (paid)'). An agent can distinguish the two without opening either 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?

Explicit when-to-use ('simple places the style doesn't have'), explicit when-not ('for a photo-like picture use generate_place'), and a prerequisite ('Call describe_drawing first for the exact format'). Nothing 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.