Skip to main content
Glama
the-real-talk

the-real-talk

create_paint_style

Create a local fill or stroke paint style from solid or gradient paints; duplicate names are refused.

Instructions

Create a local paint style (fill or stroke style) from paints (same shape as set_paints). Refuses an existing name.

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>",
      "paints": "<paints>"
    },
    "name": "create_paint_style"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
paintsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two real traits: the style is local (not a library/published style) and duplicate names are rejected rather than overwritten. It says nothing about required permissions, whether the call mutates the document, or what is returned (e.g., a style ID) for later use with apply_style.

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

Conciseness5/5

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

Two short sentences with no filler, and the core action plus the fill/stroke scope are front-loaded before the duplicate-name constraint.

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 two-parameter creation tool with no annotations and no output schema, the definition covers the essential identity, input format cross-reference, and the one surprising behavior (name collision refusal). The main remaining gap is the return value and how the created style is subsequently applied, which matters for chaining but not for calling the tool correctly.

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 0% at the top level, so the description must compensate, and it partially does: it identifies name as a uniqueness-constrained style name and paints as the same array shape as set_paints, which lets an agent reuse existing knowledge of that format. It adds nothing about the 8-paint cap or how fill vs. stroke style is chosen at creation time.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Create a local paint style'), and narrows it to fill or stroke styles, so an agent can separate it from create_effect_style and create_text_style without opening a schema. It stops short of naming those siblings explicitly, so differentiation is by noun rather than by routing.

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

Usage Guidelines2/5

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

'Refuses an existing name' is a failure condition, not guidance on when to reach for this tool. There is no mention of when to use it versus set_paints, apply_style, or the other create_*_style tools, and no prerequisites are stated.

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