Skip to main content
Glama
Sign In
DX12 Engine MCP Server

DX12 Engine MCP Server

by ryuto-alt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

名前でエンティティ検索

dx12_find_entity
Read-only

Find a game entity by exact name match. Returns entity ID and name, or null if not found.

Instructions

名前の完全一致でエンティティを1件探す。見つかれば {entityId, name}、無ければ null。

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": "dx12_find_entity"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes探すエンティティ名(完全一致)。

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the description's mention of returning null if not found adds useful behavioral context beyond what annotations provide. The description aligns with the read-only nature.

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 two sentences, front-loaded with the verb and resource, and contains no unnecessary words. Every part adds value.

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

Completeness5/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 nested objects), the description is complete. The output schema exists, so the description's mention of return format is supplementary but not required. No gaps remain.

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%, and the description repeats the schema's 'exact match' note without adding new meaning. Baseline 3 is appropriate as the schema already handles parameter semantics.

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?

The description clearly states the tool finds one entity by exact name match and returns a specific structure or null, which is a specific verb+resource combination with clear scope. It distinguishes from other entity tools like dx12_get_entity (by ID) or dx12_query_entities (complex queries).

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?

The description specifies the exact match condition, which guides when to use this tool, but does not explicitly state when not to use it or suggest alternatives among siblings. The context of exact match provides clear usage context.

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