Skip to main content
Glama
ryuto-alt

DX12 Engine MCP Server

by ryuto-alt

Luaプロパティ設定

dx12_set_lua_property
Idempotent

Modify a single LuaScript property (declared in properties) by entity id or name. If playing, the script reloads instantly; otherwise, changes apply on next play.

Instructions

LuaScript のプロパティを1つ書き換える(スクリプトの properties 宣言にあるものだけ)。type に応じて value は number/bool/string/[x,y,z]。Playing 中なら即再注入(スクリプト再ロード=OnStart 再実行)、Editor 中は保存だけで次 Play から反映。entity(id) か name 指定。型が不安なら先に dx12_get_lua_component_state で確認。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesプロパティ名(スクリプトの properties に宣言済みのもの)。
nameNoエンティティ名(完全一致)。id の代わりに使える。Stop 後など id が変わる場面で安定。
valueNo値。型はプロパティに合わせる: number / bool / string / [x,y,z](vec3,color)。
entityNoエンティティ id(int)。name と排他。

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNoエンジンからの生の結果。実際の形は各ツールの説明 / dx12_describe_components を参照。text にも同内容を JSON 文字列で格納。
Behavior5/5

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

Beyond annotations (idempotentHint=true, openWorldHint=false), description reveals critical side effects: immediate script reload and OnStart re-execution while playing, and deferred reflection in editor. This is essential behavioral context not captured by annotations.

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

Conciseness5/5

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

The description is a single paragraph with clear front-loading (first sentence states core purpose), followed by specific behavioral distinctions and a practical tip. Every sentence serves a distinct purpose with no redundancy.

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 and the presence of an output schema (not shown), the description adequately covers functionality. However, it does not address error cases (e.g., property not found, invalid entity) or specify the output schema format, leaving minor gaps for an AI agent.

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?

With 100% schema description coverage, baseline is 3. The description adds value by clarifying value types according to property type (number/bool/string/vec3) and explaining the mutual exclusivity of entity and name, plus a tip for type confirmation. This elevates it to 4.

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 the tool rewrites a single LuaScript property, specifying the allowed value types (number/bool/string/[x,y,z]) and the constraint that only properties declared in the script's properties are modifiable. This distinguishes it from sibling tools like dx12_set_component which is more general.

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?

Description provides context-dependent behavior (playing vs editor) and recommends verifying type with dx12_get_lua_component_state if unsure. It explains both entity identification methods but does not explicitly state when not to use this tool or list exhaustive alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ryuto-alt/dx12-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server