Skip to main content
Glama

create_text

Creates a text object in Blender at a specified location or collection, enabling 3D text for scenes and models.

Instructions

Create a text object.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
textNoText
locationNo
collectionNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure, yet it adds nothing beyond the bare mutation verb. It does not say whether the object is added to the current scene, what happens when location or collection are omitted, or that the text parameter defaults to the literal string "Text". The one point of credit is that the verb implies a non-destructive create rather than a modify.

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

Conciseness3/5

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

The single sentence is efficient with no filler, and it is front-loaded, but its brevity reflects under-specification rather than discipline. There is no wasted wording to cut, but also nothing structured to guide the caller.

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?

An output schema exists, so return values need not be described, but for a four-parameter creation tool with zero annotation coverage and zero schema description coverage, the one-line description leaves core questions unanswered. It does not indicate where the object lands, what the defaults produce, or how this differs from the many sibling creation tools.

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

Parameters1/5

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

Schema description coverage is 0% and all four parameters (name, text, location, collection) appear with only type and default information. The description mentions none of them, so there is no explanation of coordinate space for location, whether collection refers to an existing collection by name, or how name differs from the text content.

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

Purpose3/5

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

The description states a verb and resource ("Create a text object"), which is minimally informative, but it is close to a restatement of the name create_text and does nothing to distinguish it from siblings such as create_object or create_curve. An agent knows a text object is produced but not what kind of text object or how it differs from generic object creation.

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?

There is no when-to-use guidance, no mention of prerequisites (e.g., whether a collection must already exist), and no reference to an alternative tool for creating objects or curves. The agent must infer usage entirely from the name.

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