Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

get_project_settings_value

Read-onlyIdempotent

Reads a single Unreal Engine settings class property's in-memory value as an ExportText string, returning class name, property name, and value.

Instructions

Read one property of a settings class default object (CDO) as its ExportText string; this is the in-memory value, not re-read from the .ini on disk. Returns class_name, property_name and value; an unknown class or property is an error. set_project_settings_value is the writer.

Returns: { class_name: string, property_name: string, value: string }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
class_nameYesShort name of a loaded UDeveloperSettings subclass without the U prefix (e.g. "PhysicsSettings"), or a /Script/Module.Class path
property_nameYesName of the property on the settings class, e.g. "DefaultGravityZ"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.2.0
    • changedInput schema / properties / class_name / description
      Previous value: -"Class short name or /Script/Module.Class path"New value: +"Short name of a loaded UDeveloperSettings subclass without the U prefix (e.g. \"PhysicsSettings\"), or a /Script/Module.Class path"
    • changedInput schema / properties / property_name / description
      Previous value: -"Name of the property on the settings class"New value: +"Name of the property on the settings class, e.g. \"DefaultGravityZ\""
  2. First observedv1.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower. The description adds real behavioral context beyond that: the value comes from the in-memory CDO (not the .ini on disk) and an unknown class or property is an error.

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 efficient. Minor redundancy: the return fields are stated both inline ('Returns class_name, property_name and value') and again in the trailing 'Returns:' block.

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

Completeness4/5

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

No output schema exists, but the description supplies the return shape and the error condition, and the tool is simple (2 required params). What an agent needs to call it correctly is present, though the duplicated return line slightly muddies the structure.

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 description coverage is 100% and both parameters are fully documented in the schema (including the U-prefix convention and path alternative). The description adds no parameter-level meaning beyond what the schema supplies, so the baseline 3 is correct.

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 (Read) and resource (one property of a settings class default object) and names the sibling it is not: set_project_settings_value is the writer. An agent can distinguish read from write without opening either schema.

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

Usage Guidelines4/5

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

Explicitly routes write intent to set_project_settings_value and clarifies that the value is the in-memory CDO rather than a re-read of the .ini on disk. It lacks an explicit statement of when NOT to use it beyond the writer contrast, so it falls just short of a 5.

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