Skip to main content
Glama

set_annotation_stroke_property

Set an annotation stroke's display mode to 3DSPACE, 2DSPACE, or 2DIMAGE by specifying the annotation, layer, and stroke index.

Instructions

Set a property on an annotation stroke.

Args: annotation_name: Name of the annotation data block. layer_name: Name of the layer containing the stroke. stroke_index: Index of the stroke in the layer (0-based). property: display_mode, the only stroke setting in 5.2. value: 3DSPACE (in the scene), 2DSPACE (stuck to the view) or 2DIMAGE.

Returns: Confirmation dict.

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>",
      "stroke_index": "<stroke_index>",
      "property": "<property>",
      "value": "<value>"
    },
    "name": "set_annotation_stroke_property"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYes
propertyYes
layer_nameYes
stroke_indexYes
annotation_nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.1.0
    • changedInput schema / properties / property / enum
      Previous value: -[
      -  "display_mode",
      -  "line_width",
      -  "material_index"
      -]New value: +[
      +  "display_mode"
      +]
    • addedInput schema / properties / value / enum
      Added value: +[
      +  "2DIMAGE",
      +  "2DSPACE",
      +  "3DSPACE"
      +]
  2. Changed2 schema fields changedv1.7.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / property / enum
      Added value: +[
      +  "display_mode",
      +  "line_width",
      +  "material_index"
      +]
  3. Addedv1.2.2

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that this mutates a stroke and returns a "Confirmation dict," but does not state preconditions, side effects, or what happens on invalid indices.

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-loads the purpose and uses an organized Args/Returns structure with little waste. The version note about display_mode in 5.2 is useful rather than filler.

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?

All five required parameters are documented, including enum meanings, and an output schema exists so return details need not be expanded. Missing usage context and preconditions keep it from being fully complete for a mutation tool with no annotations.

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 0%, and the description compensates fully: it documents every parameter, including that stroke_index is 0-based, that property only accepts display_mode in 5.2, and what each value enum means. This adds meaningful semantics 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?

States a specific verb and resource: "Set a property on an annotation stroke." It clearly distinguishes the operation from add_annotation_stroke/add_annotation_layer by focusing on property mutation, though it never explicitly names sibling alternatives.

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?

Provides no guidance on when to use this tool versus add_annotation_stroke or add_annotation_layer, and no prerequisites or exclusions. The only implied usage is that an annotation stroke must already exist.

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