Skip to main content
Glama
andyluu98

VN MCP Blender

by andyluu98
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

dung_tu_mo_ta

Build a complete 3D building in Blender from one structured description, eliminating the need for multiple tool calls.

Instructions

Dung ca cong trinh tu mot ban mo ta, nhanh hon goi tung tool.

Day la cach nen dung khi dung nguyen mot ngoi nha. Cau truc mo_ta:

{
  "ten": "Nha pho 5x20",
  "tang": [
    {
      "ten": "Tang 1",
      "cao_do": 0.0,
      "cao_tuong": 3.1,
      "san":  {"dinh": [[0,0],[5,0],[5,14],[0,14]], "day": 0.1},
      "tuong": [{"diem_dau": [0,0], "diem_cuoi": [5,0], "day": 0.22}],
      "cot":   [{"vi_tri": [0,0], "rong": 0.22, "sau": 0.22, "cao": 3.1}],
      "cua":   [{"tuong": 0, "khoang_cach": 1.0, "rong": 1.0,
                 "cao": 2.2, "be_cua": 0.0}]
    }
  ]
}

Truong "tuong" trong moi muc cua la so thu tu cua buc tuong trong danh sach tuong cua chinh tang do, dem tu 0.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mo_taYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses that this is a bulk creation operation, but says nothing about whether it clears or overwrites existing scene content, atomicity, error handling, or permission/rate considerations – key behavioral traits for a batch-build tool.

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?

Purpose is front-loaded, followed by the necessary structure example and a targeted clarifying note about the wall index. The example block is large but earns its place because the schema itself is empty; little is wasted.

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

Completeness3/5

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

For a nested-object tool with no output schema and no annotations, the description covers the core structure well but only shows a representative subset of fields – it omits roof (mai), stairs (cau_thang) and other elements the sibling tools imply, and never states what the call returns. Adequate to start, but not complete for building an arbitrary full house.

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

Parameters4/5

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

Schema coverage is 0% with a single opaque object parameter (additionalProperties: true), so the description must compensate. It does so with a concrete JSON example enumerating the nested fields (ten, tang, cao_do, cao_tuong, san, tuong, cot, cua) and an explicit note that the door's 'tuong' value is a 0-based wall index. It stops short of exhaustive field documentation, so not a 5.

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?

States a specific verb (dung/build) and resource (ca cong trinh / entire project) from a single description. It explicitly differentiates from the per-element siblings by noting it is 'nhanh hon goi tung tool' (faster than calling each tool), so an agent can tell it apart from dung_tuong, dung_san, dung_cot, etc.

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?

'Day la cach nen dung khi dung nguyen mot ngoi nha' gives a clear when-to-use condition (building an entire house) and implies the alternative (calling individual tools) for smaller scopes. It stops short of an explicit when-not or naming a specific sibling, so it is clear context rather than a full routing rule.

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