Skip to main content
Glama

draw_curve

Draw a quadratic Bézier curve from a start point to an end point, bending toward a control point, with adjustable smoothness.

Instructions

Draw a quadratic Bézier curve from (x0,y0) to (x1,y1) bending toward the control point (control_x, control_y). steps controls smoothness.

Coordinates: (0, 0) is the top-left pixel. x grows right, y grows DOWN. A span given as position plus size covers x .. x + width - 1, so width is a count of pixels, not an offset to the far edge.

Centring differs between primitives, so check this when aligning two shapes:

  • draw_rectangle(x, width) spans x .. x+width-1, centred on x + (width-1)/2. An even width therefore centres on a half pixel.

  • draw_ellipse(center, radius) spans center-radius .. center+radius, which is always an ODD 2*radius+1 pixels wide and always centred on a whole pixel.

  • draw_ellipse_in_box(x, y, width, height) takes the same bounding box as draw_rectangle and fills it exactly, so it is the one to use for an even diameter, a disc centred on an even canvas, or a circle that has to line up with a rectangle.

  • draw_symmetric_pixels mirrors about the canvas, not about either of the above.

Writes falling outside the canvas are dropped rather than raising. Every drawing tool reports pixels_written, and pixels_clipped when anything was dropped, so compare those against what you asked for rather than trusting ok.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
x0Yes
x1Yes
y0Yes
y1Yes
colorYes
frameNoDefault: 1.
layerNo
stepsNoDefault: 32.
filenameYes
control_xYes
control_yYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed17 schema fields changedv0.10.0
    • removedInput schema / properties / color / title
      Removed value: -"Color"
    • removedInput schema / properties / control_x / title
      Removed value: -"Control X"
    • removedInput schema / properties / control_y / title
      Removed value: -"Control Y"
    • removedInput schema / properties / filename / title
      Removed value: -"Filename"
    • addedInput schema / properties / frame / description
      Added value: +"Default: 1."
    • removedInput schema / properties / frame / title
      Removed value: -"Frame"
    • removedInput schema / properties / layer / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • removedInput schema / properties / layer / default
      Removed value: -null
    • removedInput schema / properties / layer / title
      Removed value: -"Layer"
    • addedInput schema / properties / layer / type
      Added value: +"string"
    • addedInput schema / properties / steps / description
      Added value: +"Default: 32."
    • removedInput schema / properties / steps / title
      Removed value: -"Steps"
    • removedInput schema / properties / x0 / title
      Removed value: -"X0"
    • removedInput schema / properties / x1 / title
      Removed value: -"X1"
    • removedInput schema / properties / y0 / title
      Removed value: -"Y0"
    • removedInput schema / properties / y1 / title
      Removed value: -"Y1"
    • removedInput schema / title
      Removed value: -"draw_curveArguments"
  2. First observedv0.7.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only supply readOnlyHint=false and openWorldHint=false. The description adds genuine behavioral context beyond that: out-of-canvas writes are silently dropped rather than raising, every drawing call returns pixels_written and pixels_clipped, and the agent is told not to trust `ok` alone. It does not state whether the call needs an open sprite or which cel/layer is mutated, so it is not a full 5.

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

Conciseness3/5

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

The purpose is front-loaded correctly, but the bulk of the text is a shared drawing-convention preamble about draw_rectangle, draw_ellipse, draw_ellipse_in_box, and draw_symmetric_pixels — tools other than this one. It is dense rather than padded, yet a large fraction of the content does not earn its place in a curve-specific definition.

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?

With no output schema, the description correctly steps in to describe the return payload (pixels_written, pixels_clipped) and the coordinate system and clipping policy, which is what an agent needs to call and verify this draw op. What remains missing — layer/frame targeting and preconditions — is secondary for a single-primitive draw call.

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 only 18% (basically just the two defaults), so the description has to carry the load. It explains the six geometric coordinates and gives `steps` a meaning ('controls smoothness'), but leaves frame, layer, and filename semantically undocumented. Partial compensation for a low-coverage schema lands at the baseline 3.

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 opening sentence names a specific verb and resource — 'Draw a quadratic Bézier curve' — and enumerates the exact anchor and control points plus the `steps` parameter that governs it. That is precise enough to separate it from draw_line, draw_polyline, and the other drawing siblings without inspecting schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The centring section gives real routing advice (use draw_ellipse_in_box for even diameters, etc.), but it tells the agent when to prefer OTHER primitives, not when to reach for draw_curve over draw_line or draw_polyline. Usage of this tool itself is only implied by the name and the Bézier phrasing.

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

Deploy Server

Other Tools