Skip to main content
Glama

add_annotation_stroke

Creates a stroke on a specified annotation layer using XYZ points, enabling precise annotation creation in Blender.

Instructions

Add a stroke to an annotation layer.

Creates a new stroke with the given points on the specified layer. Annotation points in 5.2 are a position only: no pressure or strength.

Args: annotation_name: Name of the annotation data block. layer_name: Name of the layer to add the stroke to. points: List of XYZ coordinates, e.g. [[0,0,0], [1,1,0], [2,0,0]]. Maximum 10000 points.

Returns: Confirmation dict with point count.

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": {
      "annotation_name": "<annotation_name>",
      "layer_name": "<layer_name>",
      "points": "<points>"
    },
    "name": "add_annotation_stroke"
  }
}

Input Schema

NameRequiredDescriptionDefault
pointsYes
layer_nameYes
annotation_nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.1.0
    • removedInput schema / properties / pressure
      Removed value: -{
      -  "default": 1,
      -  "title": "Pressure",
      -  "type": "number"
      -}
  2. Addedv1.2.2

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations available, the description carries the full behavioral burden. It usefully discloses that a new stroke is created, that points are position-only without pressure or strength, the 10000-point cap, and that a confirmation dict with point count is returned, but it omits prerequisites such as whether the annotation and layer must already exist and what coordinate space the points use.

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?

The description is front-loaded with the core action, then uses compact Args and Returns sections. Every sentence adds useful information about the operation, point format, limits, or return value.

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?

Given that an output schema exists, the description need not fully explain return values, and it still mentions the confirmation dict. It documents all parameters and key limits, though it could state whether the target annotation/layer must pre-exist and what coordinate space the XYZ points are in.

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 description coverage is 0%, so the description must compensate, and it does: annotation_name and layer_name are identified as names of the target data block and layer, while points is documented with an XYZ coordinate example and a maximum count. All three parameters receive meaningful semantic detail beyond the bare schema.

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?

The first sentence states a specific verb and resource: adding a stroke to an annotation layer. It is clear enough to distinguish this from layer creation or annotation creation, but it does not explicitly name sibling alternatives, so it falls just short of the top score.

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?

The description explains what the tool does and documents its arguments, but it gives no explicit guidance on when to use this versus related tools such as add_annotation_layer, create_annotation, or add_gp_stroke. The annotation-point note is contextual, not usage guidance.

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