Skip to main content
Glama

Add vector graphic

add_vector_graphic

PROJECT-SCOPED: this call acts only on the explicit project_id and returns the project identity with its result. Add a renderer-native VECTOR graphic over a PROGRAM-time window. Kinds: rectangle (panel/highlight), ellipse, line (underline or connector), arrow, ring (point at a real visible subject/UI target), progress (a truthful completion indicator). x/y are frame-fraction centres; width/height are frame fractions. color/stroke_color/background_color are #RRGGBB; stroke_width is a fraction of the short frame edge; rounding is 0-0.5 of the shape's short side; progress value is 0-1. motion uses the same LOCAL x/y/scale/rotation/opacity keyframes as designed text. These are compositional primitives, not decoration quotas: use a panel to support hierarchy, a line to connect, and arrows/rings only when the frame contains the thing they identify. Preview the whole path before accepting it.

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
endYes
kindYes
colorNo
startYes
valueNo
widthNo
heightNo
motionNoElement-local motion curves. t is seconds from this text's own start; x/y are frame fractions, scale is relative, rotation is degrees, opacity is 0..1.
opacityNo
roundingNo
project_idYesRequired immutable scope for this call. Copy the id from list_projects/open_project/project_state; the active-project pointer is never used to guess.
motion_motifNoActive Blueprint motion motif id this event executes; never 'hold'.
stroke_colorNo
stroke_widthNo
background_colorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / motion / properties / opacity / anyOf
      Previous value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "items": {
      -      "properties": {
      -        "ease": {
      -          "enum": [
      -            "linear",
      -            "in",
      -            "out",
      -            "in_out",
      -            "hold"
      -          ],
      -          "type": "string"
      -        },
      -        "t": {
      -          "type": "number"
      -        },
      -        "v": {
      -          "type": "number"
      -        }
      -      },
      -      "required": [
      -        "t",
      -        "v"
      -      ],
      -      "type": "object"
      -    },
      -    "minItems": 1,
      -    "type": "array"
      -  }
      -]New value: +[
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "items": {
      +      "properties": {
      +        "ease": {
      +          "enum": [
      +            "linear",
      +            "in",
      +            "out",
      +            "in_out",
      +            "hold"
      +          ],
      +          "type": "string"
      +        },
      +        "t": {
      +          "minimum": 0,
      +          "type": "number"
      +        },
      +        "v": {
      +          "type": "number"
      +        }
      +      },
      +      "required": [
      +        "t",
      +        "v"
      +      ],
      +      "type": "object"
      +    },
      +    "maxItems": 24,
      +    "minItems": 1,
      +    "type": "array"
      +  }
      +]
    • changedInput schema / properties / motion / properties / rotation / anyOf
      Previous value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "items": {
      -      "properties": {
      -        "ease": {
      -          "enum": [
      -            "linear",
      -            "in",
      -            "out",
      -            "in_out",
      -            "hold"
      -          ],
      -          "type": "string"
      -        },
      -        "t": {
      -          "type": "number"
      -        },
      -        "v": {
      -          "type": "number"
      -        }
      -      },
      -      "required": [
      -        "t",
      -        "v"
      -      ],
      -      "type": "object"
      -    },
      -    "minItems": 1,
      -    "type": "array"
      -  }
      -]New value: +[
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "items": {
      +      "properties": {
      +        "ease": {
      +          "enum": [
      +            "linear",
      +            "in",
      +            "out",
      +            "in_out",
      +            "hold"
      +          ],
      +          "type": "string"
      +        },
      +        "t": {
      +          "minimum": 0,
      +          "type": "number"
      +        },
      +        "v": {
      +          "type": "number"
      +        }
      +      },
      +      "required": [
      +        "t",
      +        "v"
      +      ],
      +      "type": "object"
      +    },
      +    "maxItems": 24,
      +    "minItems": 1,
      +    "type": "array"
      +  }
      +]
    • changedInput schema / properties / motion / properties / scale / anyOf
      Previous value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "items": {
      -      "properties": {
      -        "ease": {
      -          "enum": [
      -            "linear",
      -            "in",
      -            "out",
      -            "in_out",
      -            "hold"
      -          ],
      -          "type": "string"
      -        },
      -        "t": {
      -          "type": "number"
      -        },
      -        "v": {
      -          "type": "number"
      -        }
      -      },
      -      "required": [
      -        "t",
      -        "v"
      -      ],
      -      "type": "object"
      -    },
      -    "minItems": 1,
      -    "type": "array"
      -  }
      -]New value: +[
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "items": {
      +      "properties": {
      +        "ease": {
      +          "enum": [
      +            "linear",
      +            "in",
      +            "out",
      +            "in_out",
      +            "hold"
      +          ],
      +          "type": "string"
      +        },
      +        "t": {
      +          "minimum": 0,
      +          "type": "number"
      +        },
      +        "v": {
      +          "type": "number"
      +        }
      +      },
      +      "required": [
      +        "t",
      +        "v"
      +      ],
      +      "type": "object"
      +    },
      +    "maxItems": 24,
      +    "minItems": 1,
      +    "type": "array"
      +  }
      +]
    • changedInput schema / properties / motion / properties / x / anyOf
      Previous value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "items": {
      -      "properties": {
      -        "ease": {
      -          "enum": [
      -            "linear",
      -            "in",
      -            "out",
      -            "in_out",
      -            "hold"
      -          ],
      -          "type": "string"
      -        },
      -        "t": {
      -          "type": "number"
      -        },
      -        "v": {
      -          "type": "number"
      -        }
      -      },
      -      "required": [
      -        "t",
      -        "v"
      -      ],
      -      "type": "object"
      -    },
      -    "minItems": 1,
      -    "type": "array"
      -  }
      -]New value: +[
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "items": {
      +      "properties": {
      +        "ease": {
      +          "enum": [
      +            "linear",
      +            "in",
      +            "out",
      +            "in_out",
      +            "hold"
      +          ],
      +          "type": "string"
      +        },
      +        "t": {
      +          "minimum": 0,
      +          "type": "number"
      +        },
      +        "v": {
      +          "type": "number"
      +        }
      +      },
      +      "required": [
      +        "t",
      +        "v"
      +      ],
      +      "type": "object"
      +    },
      +    "maxItems": 24,
      +    "minItems": 1,
      +    "type": "array"
      +  }
      +]
    • changedInput schema / properties / motion / properties / y / anyOf
      Previous value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "items": {
      -      "properties": {
      -        "ease": {
      -          "enum": [
      -            "linear",
      -            "in",
      -            "out",
      -            "in_out",
      -            "hold"
      -          ],
      -          "type": "string"
      -        },
      -        "t": {
      -          "type": "number"
      -        },
      -        "v": {
      -          "type": "number"
      -        }
      -      },
      -      "required": [
      -        "t",
      -        "v"
      -      ],
      -      "type": "object"
      -    },
      -    "minItems": 1,
      -    "type": "array"
      -  }
      -]New value: +[
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "items": {
      +      "properties": {
      +        "ease": {
      +          "enum": [
      +            "linear",
      +            "in",
      +            "out",
      +            "in_out",
      +            "hold"
      +          ],
      +          "type": "string"
      +        },
      +        "t": {
      +          "minimum": 0,
      +          "type": "number"
      +        },
      +        "v": {
      +          "type": "number"
      +        }
      +      },
      +      "required": [
      +        "t",
      +        "v"
      +      ],
      +      "type": "object"
      +    },
      +    "maxItems": 24,
      +    "minItems": 1,
      +    "type": "array"
      +  }
      +]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false) but not scoping or side effects. The description adds that the call is PROJECT-SCOPED, acts only on the explicit project_id, and returns the project identity with its result — genuinely useful behavior beyond the annotations. It does not mention auth requirements, undo semantics, or what happens on invalid geometry, so it is strong but not exhaustive.

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?

The scoping constraint is front-loaded and each subsequent sentence adds parameter or usage information rather than filler. It is dense and long, but the length is justified by the 17-parameter surface; a slightly tighter phrasing of the kind semantics could shave words without losing meaning.

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 mutation tool with 17 parameters, nested motion objects, low schema coverage, and no output schema, the description covers geometry units, color formats, rounding bounds, progress range, motion keyframe model, and project scoping. Missing pieces such as start/end timing semantics and how motion_motif interacts with the Blueprint motif system keep it from being fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 18% (17 params, effectively two documented), so the description must carry the load — and it largely does: it defines x/y as frame-fraction centres, width/height as frame fractions, color/stroke_color/background_color as #RRGGBB, stroke_width as a fraction of the short frame edge, rounding as 0-0.5, progress value as 0-1, and motion as LOCAL x/y/scale/rotation/opacity keyframes. It still leaves start/end window semantics and opacity/motion_motif partially implicit, so it compensates well but not completely.

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 ('Add a renderer-native VECTOR graphic over a PROGRAM-time window') and enumerates the six supported kinds with their intended semantic roles (panel/highlight, underline/connector, etc.). This is enough to distinguish it from siblings like add_motion_graphic, add_ui_scene, and add_custom_filter without opening their schemas.

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 real when-to-use guidance per kind ('use a panel to support hierarchy, a line to connect, and arrows/rings only when the frame contains the thing they identify') plus the workflow caveat 'Preview the whole path before accepting it.' It stops short of naming sibling alternatives (set_vector_graphic, remove_vector_graphic, add_motion_graphic) to route between them, so it is clear context rather than full when/when-not/alternatives guidance.

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.