Skip to main content
Glama

configure_gravity

DestructiveIdempotent

Set Unreal Engine world gravity from named presets such as Earth, Moon, Mars, Zero, Low, High, Enabled, or Disabled, with old/new values and a physics-component census returned.

Instructions

Set world gravity from a named preset (Earth -980, Moon -163, Mars -371, Zero, Low, High -1960, Enabled, Disabled), writing the same WorldSettings fields as set_world_gravity and returning old/new/requested triplets plus a physics-component census of the world. Prefer set_world_gravity when you have an exact number. WARNING: gravity_configured is a real re-read (it compares GlobalGravityZ against what was asked), but an UNRECOGNISED preset name is NOT an error: it comes back gravity_configured:false with the reason in gravity_message and nothing written -- read that field, not the envelope.

Returns: { gravity_settings: string, gravity_configured: bool, gravity_message: string, old_gravity_x: float, old_gravity_y: float, old_gravity_z: float, old_gravity_enabled: bool, new_gravity_x: float, new_gravity_y: float, new_gravity_z: float, new_gravity_enabled: bool, requested_gravity_x: float, requested_gravity_y: float, requested_gravity_z: float, requested_gravity_enabled: bool, world_name: string, world_physics_enabled: bool, world_physics_delta_time: float, world_physics_time_seconds: float, world_physics_real_time_seconds: float, world_physics_component_count: int, world_simulate_physics_component_count: int, world_dynamic_physics_component_count: int, gravity_impact: float, gravity_impact_rating: string, gravity_recommendations: [string] }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
gravity_settingsYesPreset NAME, one of 'Enabled'/'Disabled', 'Earth' (-980), 'Moon' (-163), 'Mars' (-371), 'Zero', 'Low', 'High', in any capitalisation ('EARTH' works too). For an arbitrary number use set_world_gravity.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare non-readOnly, idempotent, destructive. The description goes well beyond them: it discloses that gravity_configured is a genuine re-read comparison, and that an unrecognised preset returns gravity_configured:false with the reason in gravity_message and NOTHING WRITTEN. That failure-mode detail is high-value behavioural context not derivable from annotations.

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-loads the action, presets, and alternative before the WARNING. The embedded Returns block is justified because no output schema exists, but the preset list overlaps the schema's enumeration, so it is not maximally tight.

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?

With no output schema, the description supplies the full return shape (old/new/requested triplets, physics census, impact fields) and covers the key edge case and the sibling alternative. Nothing needed to call it correctly 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 description coverage is 100% and the schema already lists the valid preset names and capitalisation tolerance. The description's preset enumeration (with numeric values like Earth -980) largely repeats the schema, so baseline 3 is appropriate.

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+resource (set world gravity from a named preset), enumerates the exact preset values, and explicitly names the sibling set_world_gravity. An agent can distinguish it from set_world_gravity (exact number) 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 Guidelines5/5

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

Explicitly says 'Prefer set_world_gravity when you have an exact number', giving the alternative and the selecting condition. It also warns that an unrecognised preset is not an error and tells the agent which field to read, so the calling conditions are fully covered.

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