blender-mcp

by kleer001

Overview Schema Source Related Servers Discussions Admin

Python

Local

create_gp_stroke

Create a Grease Pencil stroke from a list of points, specifying coordinates, pressure, and strength for each vertex.

Instructions

Create a stroke from point list. Each point: {co: [x,y,z], pressure: float, strength: float}.

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": {
      "object": "<object>",
      "layer": "<layer>",
      "points": "<points>"
    },
    "name": "create_gp_stroke"
  }
}

Input Schema

Name	Required	Description	Default
`frame`	No
`layer`	Yes
`object`	Yes
`points`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 10, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations, the description must disclose behavioral traits, but it does not address side effects, error conditions, coordinate space, or how the tool interacts with existing strokes/layers. It only defines the input format, leaving the agent without information about what happens when the stroke is created.

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 a single sentence that front-loads the core purpose and includes a compact data format example. Every word earns its place; no filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 4 parameters (3 required), a minimal schema, and no annotations, the description is insufficiently complete. It does not explain how object/layer are used, the meaning of frame, return values, or failure modes, making it hard for an agent to safely predict the tool's behavior.

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 coverage is 0%, so the description must compensate. It does explain the 'points' parameter structure ({co, pressure, strength}), which is valuable, but it leaves 'object', 'layer', and 'frame' entirely undocumented. The partial compensation is useful but incomplete.

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?

The description states a clear action ('Create a stroke') and specific input ('from point list'), distinguishing it from sibling GP tools like add_gp_layer or create_grease_pencil. It also provides a concise data format for the points, making the tool's purpose unambiguous.

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?

No guidance is given on when to use this tool versus alternatives, nor are prerequisites mentioned (e.g., needing an existing GP object/layer). The description only states what the tool does, not the context in which it should be invoked.

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

Deploy Server