Skip to main content
Glama
ryuto-alt

DX12 Engine MCP Server

by ryuto-alt
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

ネットワークテストロール設定

dx12_net_setup
Idempotent

Configure the network role for multiplayer testing in DX12 Engine. Choose host, client, or offline mode to set up listen server or connect to an address.

Instructions

次の dx12_play で自動 Host/Join するロールを設定する(ツールバーの Play ロールドロップダウンと同じ)。典型フロー: ①複製したいエンティティに set_component で networkIdentity + networkTransform を付ける → ②net_setup(role='host') → ③dx12_play → ④dx12_net_launch_test_client → ⑤dx12_net_status で players/RTT を確認。role='offline' で解除。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
portNoclient 時の接続先ポート。省略/0 でエンジン設定の defaultPort。
roleYeshost=リッスンサーバー / client=address へ接続 / offline=マルチプレイ無効。
addressNoclient 時の接続先 IP。省略で現状維持(既定 127.0.0.1)。

Output Schema

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

Tool Definition Quality

A3.9/5.0
Behavior4/5

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

Annotations already indicate idempotentHint true. Description adds context about offline reset and typical flow, but does not contradict annotations.

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?

Front-loaded with purpose, then provides a typical flow. No wasted words, but could be slightly more compact. Good structure.

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?

Tool is simple; description covers usage flow and behavior. Output schema exists (though not shown) so return values not needed. Adequate for the tool's complexity.

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% with descriptions. The description does not add significant new meaning beyond the schema; it only repeats or slightly rephrases schema info.

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 clearly states it sets the network role for automatic host/join in dx12_play, and includes a typical flow. It distinguishes from siblings implicitly through the flow, but no explicit differentiation.

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?

Provides a typical flow (steps 1-5) showing when to use this tool. Does not explicitly state when not to use or alternatives, but the flow is clear guidance.

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