Probe local and LAN open-source game-development tools—Blender, ComfyUI, UniRig, Godot, LibreSprite, and Ollama—to confirm they are reachable before building asset pipelines.
Live probe of your local & LAN open-source game development ecosystem (BlenderMCP socket, Blender CLI, ComfyUI, TRELLIS/Hunyuan3D/UniRig, Godot 4, LibreSprite/Aseprite, Ollama).
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v2.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. 'Live probe' usefully signals active checking (not cached config) and that LAN endpoints may be contacted, which hints at latency/availability dependence. But it says nothing about behavior when a tool is missing (error vs. reported absence), timeouts, or whether probing is side-effect free.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with the verb and scope first and the enumerated targets after; nothing is redundant. The parenthetical list is long but each entry carries real disambiguating information, so it largely earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
There is no output schema and no annotations, so the description is the only source of truth about what comes back. It does not indicate the result shape (e.g. per-tool availability/version/path), how unavailable tools are represented, or how expensive the probe is — gaps that matter for a tool whose entire purpose is producing a status report.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly avoids inventing parameter claims that the empty schema would contradict.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific action (live probe / discovery) and enumerates exactly what is being discovered: BlenderMCP socket, Blender CLI, ComfyUI, TRELLIS/Hunyuan3D/UniRig, Godot 4, LibreSprite/Aseprite, Ollama. The parenthetical list makes it distinguishable from the narrower sibling gameforge_introspect_comfyui, though it never explicitly says 'this is the broad version of X'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is only implied: an agent can infer it should run this to learn what local tooling exists before choosing a pipeline tool. There is no explicit when-to-use/when-not, no statement that it is a read-only prerequisite step, and no pointer to gameforge_introspect_comfyui as the narrower alternative.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.