Skip to main content
Glama

get_project_settings

Read-only

Parse project.godot into JSON without launching Godot to inspect display, input, and rendering settings; optionally filter to one INI section.

Instructions

Parse project.godot into JSON without launching Godot. Use to inspect display, input and rendering settings. Pass section for one INI section. Returns: settings as { [section]: { [key]: value } }, or { [key]: value } plus section. Strings are unescaped, an empty value is null, complex values stay raw text. Keys before any section are under global. warnings leads when the section is absent, a value is unterminated or empty, a line is not as Godot writes it, or a setting is assigned twice.

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": {
      "projectPath": "<projectPath>"
    },
    "name": "get_project_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectionNoFilter to a specific INI section (e.g. "display", "application"). Omit for all sections; an empty string is treated as omitted.
projectPathYesPath to the Godot project directory

Output Schema

NameRequiredDescriptionDefault
sectionNoPresent when a section filter was applied.
settingsYesWithout section: { [section]: { [key]: value } }. With section: { [key]: value }. A value is a string, number, boolean or null (an empty value).
warningsNoPresent only when there is something to say. One entry names, by line number, every line that is not in the form Godot writes (two statements on a line, a statement after a header, a # line, a value that is not one whole value): the engine may read such a line differently from what settings shows.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv4.0.1
    • changedInput schema / properties / section / description
      Previous value: -"Filter to a specific INI section (e.g. \"display\", \"application\"). Omit for all sections."New value: +"Filter to a specific INI section (e.g. \"display\", \"application\"). Omit for all sections; an empty string is treated as omitted."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "section": {
      +      "description": "Present when a section filter was applied.",
      +      "type": "string"
      +    },
      +    "settings": {
      +      "description": "Without section: { [section]: { [key]: value } }. With section: { [key]: value }. A value is a string, number, boolean or null (an empty value).",
      +      "type": "object"
      +    },
      +    "warnings": {
      +      "description": "Present only when there is something to say. One entry names, by line number, every line that is not in the form Godot writes (two statements on a line, a statement after a header, a # line, a value that is not one whole value): the engine may read such a line differently from what settings shows.",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "settings"
      +  ],
      +  "type": "object"
      +}
  2. Addedv3.1.1
  3. Removedv3.0.0
  4. Addedv1.0.0

TDQS

A4.2/5.0
Behavior5/5

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

Annotations only declare readOnlyHint, so the description carries the real burden and does: no Godot process is launched, unescaping rules, empty values become null, complex values stay raw, pre-section keys land under __global__, and warnings lead when a section is absent or a line is malformed. These are exactly the non-obvious behaviors an agent needs before trusting the output.

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?

Front-loaded with the core action and tight throughout, with no filler sentences. The return-shape and warnings clauses are dense run-ons that take a second pass to parse, which slightly hurts readability.

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?

Despite having an output schema, the description still spells out the malformed-input behavior and the warning conditions an agent must handle on failure. For a two-parameter read tool, nothing needed to call it or interpret its edge cases is missing.

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%, so both parameters are already documented, including the empty-string-equals-omitted rule. The description restates 'Pass section for one INI section' without adding format or matching semantics beyond what the schema provides; baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb and resource ('Parse project.godot into JSON') plus a disambiguating constraint ('without launching Godot') and the setting domains covered. An agent can tell this is a passive config-file reader, distinct from write-side siblings like set_project_setting or dependency tools like get_scene_dependencies.

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?

'Use to inspect display, input and rendering settings' gives implied context but names no alternative and no exclusion. It never tells the agent to prefer this over check_project or to use set_project_setting for mutation, leaving the routing decision to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.