Editor toolsets

Agentic Biomes registers 28 editor tools with Epic's experimental ToolsetRegistry plugin: 25 in AgenticBiomeToolset and 3 in AgenticCaptureToolset. Each tool is listed once below under its C++ name. For how to connect an MCP client and a safe order of calls, see Agent toolsets.

Conventions

• Toolset names. The registry names a toolset after the module that owns it plus the class name, so the two toolsets are AgenticBiomesToolsets.AgenticBiomeToolset and AgenticBiomesToolsets.AgenticCaptureToolset. A tool is addressed as ToolsetName.ToolName, split at the last dot, for example AgenticBiomesToolsets.AgenticBiomeToolset.InspectBiome. Through the call_tool meta tool the two parts go in separate arguments, toolset_name and tool_name.
• Argument and field names on the wire. The tables use the C++ names. Over MCP the first letter of every argument and every result field is lowercased, so BiomePath is sent as biomePath and speciesId comes back for SpeciesId. A name that already starts in lowercase, such as bDryRun, is unchanged. describe_toolset returns the exact schema for your engine build; treat it as the authority.
• Asset references inside objects. A species row stores its Mesh and Generator as asset references. In JSON a reference is an object with one key, {"refPath": "/Path/Asset.Asset"}, and a plain string with the same content is also accepted. The path must be an object path with the dot and asset name; a bare package path is refused. Arguments typed as plain strings, such as BiomePath, are not reference objects.
• Results. The editor wraps every result as an object with the value under returnValue. Enumerations come back as their names. A call with a missing argument or a value of the wrong shape fails before the tool runs, with an error from the registry.
• Required arguments. Every argument is required unless its row gives a default. Only DrawSplineBiome.bLinear (default true) and FoldMeshTerrainSibling.bSplitOnConflict (default false) have defaults.
• Path forms. BiomePath accepts a package path such as /AgenticBiomes/Biomes/Showcase/Biome_Desert or the full object path with the dot. Graph, layer-info and reference arguments are loaded as objects, so give them the full object path (/Path/Asset.Asset). Subject for the proof tools is a package path without the dot.
• Threading. Tools run on the editor's game thread. The editor is busy until a call returns, and the long calls (BuildMeshTerrain, HashBiomes, ProveUnreferencedMany, a first CaptureShot) can take a while.
• What is saved. SetSpecies, live runs of MigrateEnumValues and FoldMeshTerrainSibling, SetRuntimeAssetScale and the four graph-parameter tools save the asset they edit. PaintBiomeLayers saves any layer-info assets it creates, and BuildBiomesFromPaint writes its biome-map texture. Tools that act on the open level (BuildLevel, BuildLevelAs, DrawSplineBiome, PaintLayerRect, PaintBiomeLayers, BuildBiomesFromPaint, AddLandscapeTargetLayer, ImportHeightmapTerrain) change the level in memory and do not save it: save the level yourself. BuildMeshTerrain is the exception in the other direction. It refuses to start while the editor holds unsaved world packages.
• Missing assets. Most tools report a path that does not load as text or in a problem list. InspectBiome, FingerprintBiome and HashBiomes do not: they return an empty list.

AgenticBiomeToolset

Registered name AgenticBiomesToolsets.AgenticBiomeToolset. 25 tools. "Blocking" means the result describes finished work when the call returns.

Species view, InspectBiome

Edit result, SetSpecies

Issues, ValidateBiome

Each issue has severity (Error or Warning), code, speciesId (None when the finding is about the biome as a whole) and detail.

Migration report, MigrateEnumValues

Fold report, FoldMeshTerrainSibling

Terrain resolution, ResolveTerrainBackend

Build result, BuildLevel and BuildLevelAs

Gate, VerifyLevel

status is decided in this order:

Refused is returned instead when the level does not contain exactly one Terraformer; rendered carries the reason.

Fingerprints and hashes

Death certificate, ProveUnreferenced and ProveUnreferencedMany

Limits to know before trusting a certificate. The byte scan looks only for paths under /AgenticBiomes/, so for an asset outside that mount only the registry channel can find references. A name that does not start with / is treated as a class name and is not checked for existence. A path assembled from fragments at runtime, and references from other plugins or projects, are invisible to every channel. Treat bSafeToDelete as evidence, not a guarantee.

AgenticCaptureToolset

Registered name AgenticBiomesToolsets.AgenticCaptureToolset. 3 tools. They read a shot set from a JSON file that you supply and photograph the open level from fixed cameras. There is deliberately no "capture all" tool: each call handles one shot, so the editor gets real frames between shots.

Shot-set file

The shot set is your file, and the plugin ships none. Every capture call takes it as ShotSetPath: a path to a .json file in your project, either absolute or relative to the project directory (the folder that holds your .uproject). The capture tools do not write it. They refuse, and report the reason in problem with the expected format appended, when ShotSetPath is empty, does not end in .json, cannot be read, is not valid JSON, has no levels array, or declares no entry for the LevelPath you passed. A level entry with no shots array, or whose shots all fail to parse, is refused with its own problem.

A minimal file with one shot looks like this:

{
  "levels": [
    {
      "level": "/Game/Maps/MyMap",
      "shots": [
        {
          "id": "A_wide",
          "kind": "wide",
          "purpose": "what this camera shows",
          "fov": 70,
          "location": [0, 0, 0],
          "rotation": {"roll": 0, "pitch": -35, "yaw": 0}
        }
      ]
    }
  ]
}

Leave location at [0, 0, 0] when you do not know where the camera should stand, open the level, and call DeriveCameras. It measures real positions from the open level and returns them as literals. Write each returned location into the file (and its rotation, which carries the derived yaw), then call DescribeShotSet to confirm bDerived is true. CaptureShot refuses a shot that still has the [0, 0, 0] placeholder rather than photographing the world origin.

Shot set info, DescribeShotSet

Shot result, CaptureShot

Camera derivation, DeriveCameras

How cameras are placed: a wide shot stands off along the regions' spread so all regions fit the shot's field of view. Any other shot stands on the boundary between the two closest regions (on a texture-driven level, on a biome-map cell edge), at 40 cm for ground, 200 cm for silhouette and 170 cm for every other kind.

Report text

Tools that return text give the reason in the string. These are the strings you will see, with <...> standing for a value.

While BuildMeshTerrain runs, the Output Log (category LogAgenticBiomes) shows a BuildMeshTerrain: STARTING line and, when it ends, a BuildMeshTerrain: FINISHED success=... line. If your client times out first, read the outcome there instead of calling again.

What the toolsets do not do

• There is no tool to delete a species row, a region, an actor or an asset, to clear a level, or to save a level.
• No tool edits roads, exclusion zones, the wind bridge or the terrain material; use the Details panel. Runtime ground cover has no authoring tool of its own: SetRuntimeAssetScale rescales a runtime template, the PCG graph-parameter tools reach graph parameters, and SetSpecies writes a row's runtime options along with the rest of the row. Everything else about it is edited in the Details panel.
• Most Terraformer buttons have no tool. Auto Grid, Validate Biome Palette, Audit Biome Map, Bake Banded Biome Map, Clear Biome Map and Regenerate Edited Area are Details-panel buttons, not tools. The tools build, paint, draw and verify; they do not set up a sector grid or a biome-map palette for you.
• InspectBiome returns a summary view of each row, not every field. Read a full row in the Details panel before replacing it with SetSpecies.
• BuildLevel repeats the builder the Terraformer last recorded, so it cannot start a level that has never been built. Use BuildLevelAs with the builder you want for the first build. BuildLevelAs does not convert a built level to a different builder: it refuses when the recorded builder differs from the one you name, and when the record is Unknown but the level already has regions or placed instances. To change a built level's builder, clear the level deliberately first.
• VerifyLevel counts and checks provenance. It does not judge how the level looks.

See Agent toolsets for the workflow, the Terraformer reference and the biome asset reference. Support: Discord.