Skip to main content
Glama

list_modifiers

Lists modifiers on a Blender object with their settings, helping inspect and verify the object's modifier stack before editing or rendering.

Instructions

List modifiers on an object with settings.

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": {
      "name": "<name>"
    },
    "name": "list_modifiers"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/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 disclosure burden, and it discloses almost nothing: no ordering, no indication of whether the object must be selected/active, whether disabled modifiers are included, or whether this is purely read-only. 'With settings' hints that per-modifier settings accompany the list, which is the only behavioral signal present.

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?

It is a single short sentence with the verb front-loaded, which is good, but the brevity comes at the cost of clarity — 'with settings' is a dangling qualifier that raises more questions than it answers rather than earning its place.

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 explained, and there is only one parameter. Even so, the description leaves the parameter's meaning undefined and gives no behavioral context for a tool with zero annotation coverage, which is insufficient for correct invocation.

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

Parameters2/5

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

Schema description coverage is 0% for the single required parameter 'name', so the description must explain it. 'On an object' weakly implies the name identifies a Blender object, but it never says so, nor whether it accepts an object name, a data-block name, or a selected-object reference.

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 verb 'List' plus resource 'modifiers on an object' is more specific than the bare name, but the trailing phrase 'with settings' is ambiguous — it is unclear whether settings are included in the listing, or whether only modifiers that have settings are returned. The description also does not distinguish this from the sibling get_modifiers, so an agent cannot tell the two apart from the text alone.

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 statement of when to use this tool versus get_modifiers or the add_modifier/apply_modifier siblings. No prerequisites, no conditions, no exclusions — the only information is the name-plus-resource restatement.

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