Skip to main content
Glama
Sign In
Godot MCP

Godot MCP

by KeeVeeG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

set_custom_features

Define custom feature tags to control conditional compilation and export settings in Godot projects.

Instructions

Set custom feature tags for conditional compilation and export

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

Input Schema

NameRequiredDescriptionDefault
featuresNoList of custom feature tags (e.g. ['demo', 'mobile', 'premium'])

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

B3.1/5.0
Behavior2/5

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

No annotations exist, so the description must disclose behavioral traits. It states 'Set' implying a write operation, but does not mention reversibility, side effects, or requirements like an open project. This is insufficient for a mutation tool.

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?

Single sentence with no filler words. All information is front-loaded and every word contributes meaning.

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?

Given the tool's simplicity (one optional param, no output schema), the description is minimal but sufficient for basic understanding. However, it lacks behavioral transparency and usage context, which slightly reduces completeness.

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 the parameter 'features' already described with an example. The description adds no additional semantic information, so baseline score of 3 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 clearly states that the tool sets custom feature tags for conditional compilation and export. The verb 'Set' and resource 'custom feature tags' are specific, and the purpose is distinct from sibling tools, which focus on different settings.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives, nor any conditions or prerequisites. The description is purely declarative with no contextual use-case information.

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