Skip to main content
Glama
Sign In
bambu-printer-mcp

bambu-printer-mcp

by DMontgomery40
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

blender_mcp_call

Destructive

Invoke a discovered Blender MCP tool by exact name with schema-matched arguments to perform Blender actions; preserve results and errors, and note calls may modify the active scene.

Instructions

Call a discovered tool on the configured Blender MCP server, preserving its full MCP content and errors. Discover tool schemas with blender_mcp_status first; execute_blender_code accepts Python code and user_prompt. Calls can modify the active Blender scene and are never automatically retried.

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

Input Schema

NameRequiredDescriptionDefault
argumentsNoArguments matching the remote tool's discovered input schema. Preserve the user's own words in user_prompt when the remote tool requests it.
tool_nameYesExact name advertised by Blender MCP, such as get_scene_info or execute_blender_code.
timeout_msNoTotal connection, discovery, and tool deadline in milliseconds; defaults to BLENDER_MCP_TIMEOUT_MS or 120000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.14

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already mark this as destructive, non-idempotent, and open-world; the description is consistent and adds genuinely new behavior: it can modify the active Blender scene, is never automatically retried, and preserves the remote tool's full MCP content and errors. It does not state what a failed or partial call leaves behind in the scene.

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?

Three compact sentences with the mutating nature and no-retry behavior placed up front. Every sentence contributes, so there is little waste; the middle sentence about execute_blender_code is the most tool-specific but still relevant.

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 generic proxy with a nested-object arguments parameter and no output schema, the definition covers discovery, execution, error preservation, and side-effect risk. Missing is any guidance on what a successful response contains (it says 'full MCP content' without saying whether that content is text or structured).

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 100%, so the baseline is 3: the schema already explains tool_name, arguments, and timeout_ms. The description adds a little meaning: tool_name must come from discovery, and when calling execute_blender_code, the arguments are Python code and user_prompt. It does not clarify how nested arguments are shaped for other remote tools.

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?

The description opens with a specific verb and resource: 'Call a discovered tool on the configured Blender MCP server.' It distinguishes itself from the discovery sibling, blender_mcp_status, but does not explicitly distinguish itself from blender_mcp_edit_model, which is also a Blender operation exposed through a different route.

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?

It gives clear preconditions before calling the tool ('Discover tool schemas with blender_mcp_status first') and a concrete usage caveat for execute_blender_code accepting Python code and user_prompt. It stops short of stating when not to use this generic proxy (for example, in favor of blender_mcp_edit_model).

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