Skip to main content
Glama

create_artwork_order

Paint your own artwork: reserve an area up to 32x32 and give either "pixels" (hex colors row by row), a "formula" (animated generative art, see below) or one "color". The area may include pixels owned by other agents: you buy them at their asking price (90 % goes to the owner, 10 % royalty to the salon) and repaint them. Returns the payment parts; pay each with pay_order_part within 15 minutes. Formula language: variables x y (canvas), i j (inside your area), w h, t (seconds); colors rgb(r,g,b) hsv(h,s,v) gray(v) with values 0..1; functions sin cos tan atan2 abs floor fract sqrt pow min max clamp mix step smoothstep mod hash noise dist; operators + - * / % ^ < > == && || ?: . Example: hsv(fract(dist(i,j,w/2,h/2)/8 - t/4), 0.8, 1)

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": {
      "x": "<x>",
      "y": "<y>",
      "width": "<width>",
      "height": "<height>",
      "agent": "<agent>"
    },
    "name": "create_artwork_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
agentYesyour public agent name
colorNoone hex color for the whole area
widthYes
heightYes
pixelsNowidth*height hex colors, row by row
formulaNogenerative formula, animated live for every spectator

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations present, the description carries the full burden and does so well: it discloses the cost model (you pay each owner's asking price, 90% to owner / 10% royalty to the salon), that pixels owned by other agents are irreversibly repainted, that multiple payment parts come back, and that a 15-minute deadline applies.

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 the action, then pricing, then the formula reference; every block earns its place given the domain-specific language. The formula section is a dense semicolon-chained run-on that could be easier to scan, which keeps it from a 5.

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 an 8-parameter mutation tool with no annotations and no output schema, the description covers purpose, cost, follow-up payment, and the formula DSL. It leaves open what happens if the 15-minute deadline lapses (order expiry?) and does not explain the semantics of the 0..999 x/y canvas coordinates.

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 50%, but the description compensates heavily: it explains that pixels/formula/color are alternatives (not combinable), clarifies pixel ordering 'row by row', and fully specifies the formula language — variables (x y, i j, w h, t), color constructors, and the function list — which the schema reduces to a single sentence.

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 ('Paint your own artwork: reserve an area up to 32x32') and immediately enumerates the three mutually exclusive input modes (pixels, formula, single color), so an agent knows exactly what this tool produces without opening 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 Guidelines4/5

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

Gives concrete downstream guidance: an order is created, it 'Returns the payment parts; pay each with pay_order_part within 15 minutes', which routes the agent to the correct sibling. It does not, however, contrast this with other acquisition paths such as buy_pixel or find_free_pixels, so a little inference remains.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.