Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

get_project_setting

Read the current value of a Godot project setting by key to inspect configuration and make informed changes.

Instructions

Get the current value of a project setting.

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": {
      "setting": "<setting>"
    },
    "name": "get_project_setting"
  }
}

Input Schema

NameRequiredDescriptionDefault
settingYesSetting key to read

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It says nothing about behavior when the key is unknown (error vs. null vs. default), whether defaults or overrides are returned, or whether reads reflect in-memory unsaved state. Only the 'read' nature is implied by the verb.

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?

One short, front-loaded sentence with no filler or redundancy. It is efficient, but the brevity is under-specification rather than disciplined concision.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a simple one-parameter read with no annotations and no output schema, so the description should at least characterize the returned value and the missing-key case. Neither is covered, leaving an agent unable to predict the result shape.

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?

The single parameter is fully documented in the schema ('Setting key to read'), so schema coverage is 100% and the baseline applies. The description adds no examples or naming conventions for keys beyond what the schema already states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The sentence gives a verb (get) and resource (project setting) but is essentially an expansion of the tool name, adding only the word 'current'. It does not distinguish this from the sibling set_project_setting (the write counterpart) or from get_project_info, which may also surface project configuration.

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?

There is no guidance on when to call this versus set_project_setting or the broader project info tools, no mention of required project context, and no hint about which setting keys are valid. The agent must infer usage entirely from the name.

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