Skip to main content
Glama
Sign In
blender-mcp-bridge

blender-mcp-bridge

by otinori
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

blender/get_object

Retrieve position, rotation, scale, and material of a specified Blender object by its name.

Instructions

指定オブジェクトの詳細（位置・回転・スケール・マテリアル）を返す

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": "blender/get_object"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesオブジェクト名

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It does not explicitly state whether the tool is read-only or has side effects, though the verb '返す' implies a read operation. A clear statement of non-destructive behavior is missing.

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 description is a single concise sentence that is front-loaded with the resource and details. It wastes no words, though it could be slightly more structured with explicit mention of input/output.

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?

Given the tool's simplicity (one parameter, no output schema), the description adequately covers the return details (position, rotation, scale, material). It lacks mention of error conditions or edge cases, but is sufficient for basic use.

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 description coverage is 100% for the single parameter 'name', so the baseline is 3. The description does not add additional semantics beyond the schema, such as example values or constraints, but does not need to due to full coverage.

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?

Description clearly states it returns object details (position, rotation, scale, material) with a specific verb '返す' (returns). It distinguishes from sibling tools like create, delete, or transform by focusing on reading object data.

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 on when to use this tool versus alternatives like list_objects or get_scene_info. The description only states what it does, leaving the agent without context on selection criteria.

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