Skip to main content
Glama
Sign In
unreal-mcp-additional-tools

unreal-mcp-additional-tools

by nodormu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

generate_project_files

Regenerate IDE project files for Visual Studio, Xcode, and Rider to keep them in sync with the current Unreal Engine project structure.

Instructions

Regenerate IDE project files (Visual Studio, Xcode, Rider).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "generate_project_files"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations (readOnly/destructive) are present, so the description carries full burden. It says 'Regenerate' which communicates a write operation, but does not disclose whether files are overwritten, if arbitrary settings/options are preserved, or if source paths are required. This is ambiguous for a regeneration action.

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?

One concise sentence, front-loaded with the core verb. No wasted words, no restating of schema because there is no schema.

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?

The description gives the tool's scope (IDE files for 3 named IDEs) and a rough action, but no output schema, no mention of file targets beyond IDE type, no prerequisites like opened project/solution, and no side-effects/consequences are explained. For a 0-param tool, it remains merely viable.

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?

Input schema is empty with first-level schema coverage at 100%? Actually properties is empty (no params). Param info is irrelevant; the description adds parameter-specific operational details. Baseline 4 is appropriate.

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?

Description uses specific verb 'Regenerate' and resource 'IDE project files (Visual Studio, Xcode, Rider)', clearly distinguishing from sibling tools focused on execution or testing. However, it doesn't contrast with related project file tools like 'build_project' or 'package_project'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The usage context is implied: regenerate project files when needing to refresh IDE project structure. It lists target IDEs but gives no explicit when-to-use or when-not-to-use guidance, and doesn't name alternatives.

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