Skip to main content
Glama

enable_toolset

Read-onlyIdempotent

Add specific tool packs or entire editor domains to the active connection, making their tools callable directly instead of via call_tool while keeping core tools listed.

Instructions

Adds packs or whole domains to this connection's tool list, so their tools are called directly instead of through call_tool; the 11 core tools are always listed. Give packs, domains or both.

A pack is the few tools of one job the core leaves out: actors (delete_actor, find_actors_by_name, spawn_actor, get_actors_by_class), levels (get_current_level, list_dirty_packages, load_level, save_level), play (capture_viewport, is_play_in_editor_active, pause_play_in_editor, resume_play_in_editor, start_play_in_editor, step_play_in_editor_frame, stop_play_in_editor), assets (get_asset_referencers, delete_asset, duplicate_asset), blueprint_authoring (add_blueprint_variable, build_blueprint_graph, create_blueprint, create_blueprint_from_actors, disconnect_pin, get_blueprint_info, remove_graph_node), data_tables (get_data_table_row, set_data_table_row_fields). A domain is every tool of one area of the editor, such as Material or Animation, and can add a hundred tools to your context: find_tools with no arguments lists the domains and their sizes. Prefer a pack when one covers the job.

It changes only which tools this connection lists, never the editor or the project, and lasts until the connection's session ends; enabling the same one again adds nothing. The server announces the new list and your client re-reads it; if your client does not, call_tool reaches the same tools. An unknown name is an error that lists the packs and the domains.

Returns: { success, packs?: [{ pack, already_listed, tools }], domains?: [{ domain, already_listed, tools }], tools_added: int, list_changed: bool, note?: string }

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "enable_toolset"
  }
}

Input Schema

NameRequiredDescriptionDefault
packsNoThe packs to add, e.g. ["actors"] or ["play", "levels"].
domainsNoThe whole domains to add, as find_tools lists them, e.g. ["Material"].

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.11.0
    • changedInput schema / properties / domains / items / enum
      Previous value: -[
      -  "AI",
      -  "Analysis",
      -  "Animation",
      -  "Asset",
      -  "Audio",
      -  "Audit",
      -  "BehaviorTree",
      -  "Blueprint",
      -  "Camera",
      -  "Chooser",
      -  "Config",
      -  "DataAsset",
      -  "Documentation",
      -  "Editor",
      -  "Engine",
      -  "Export",
      -  "GameFeatures",
      -  "GameFramework",
      -  "GameplayAbilities",
      -  "GameplayBehavior",
      -  "GameplayDebugger",
      -  "GameplayTags",
      -  "GeometryScript",
      -  "Graphics",
      -  "HLOD",
      -  "Input",
      -  "Interchange",
      -  "Level",
      -  "Lighting",
      -  "Management",
      -  "Mass",
      -  "Material",
      -  "Mesh",
      -  "Meta",
      -  "Navigation",
      -  "Networking",
      -  "Optimization",
      -  "Packaging",
      -  "Performance",
      -  "Physics",
      -  "Procedural",
      -  "Reflection",
      -  "Replication",
      -  "SaveGame",
      -  "SmartObjects",
      -  "StateTree",
      -  "Subsystem",
      -  "SubsystemAuthoring",
      -  "Testing",
      -  "Timeline",
      -  "Trigger",
      -  "UI",
      -  "USD",
      -  "UVMapping",
      -  "Water"
      -]New value: +[
      +  "AI",
      +  "Analysis",
      +  "Animation",
      +  "Asset",
      +  "Audio",
      +  "Audit",
      +  "BehaviorTree",
      +  "Blueprint",
      +  "Camera",
      +  "Chooser",
      +  "Code",
      +  "Config",
      +  "DataAsset",
      +  "Documentation",
      +  "Editor",
      +  "Engine",
      +  "Export",
      +  "GameFeatures",
      +  "GameFramework",
      +  "GameplayAbilities",
      +  "GameplayBehavior",
      +  "GameplayDebugger",
      +  "GameplayTags",
      +  "GeometryScript",
      +  "Graphics",
      +  "HLOD",
      +  "Input",
      +  "Interchange",
      +  "Level",
      +  "Lighting",
      +  "Management",
      +  "Mass",
      +  "Material",
      +  "Mesh",
      +  "Meta",
      +  "Navigation",
      +  "Networking",
      +  "Optimization",
      +  "Packaging",
      +  "Performance",
      +  "Physics",
      +  "Procedural",
      +  "Reflection",
      +  "Replication",
      +  "SaveGame",
      +  "SmartObjects",
      +  "SourceControl",
      +  "StateTree",
      +  "Subsystem",
      +  "SubsystemAuthoring",
      +  "Testing",
      +  "Timeline",
      +  "Trigger",
      +  "UI",
      +  "USD",
      +  "UVMapping",
      +  "Water"
      +]
  2. Changed3 schema fields changedv2.7.0
    • changedInput schema / properties / domains / description
      Previous value: -"The domains whose tools to add, as find_tools lists them, e.g. [\"Material\"] or [\"Animation\", \"Audio\"]."New value: +"The whole domains to add, as find_tools lists them, e.g. [\"Material\"]."
    • addedInput schema / properties / packs
      Added value: +{
      +  "description": "The packs to add, e.g. [\"actors\"] or [\"play\", \"levels\"].",
      +  "items": {
      +    "enum": [
      +      "actors",
      +      "levels",
      +      "play",
      +      "assets",
      +      "blueprint_authoring",
      +      "data_tables"
      +    ],
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "domains"
      -]
  3. Addedv2.5.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real meaning beyond them: it scopes the change to 'only which tools this connection lists, never the editor or the project', states it lasts only for the session, and explains idempotency concretely ('enabling the same one again adds nothing'). It also discloses the client-refresh mechanism and the fallback via call_tool, plus the error behavior for unknown names.

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?

The core action and the pack-vs-domain tradeoff are front-loaded, and the closing paragraph covers lifecycle and return shape efficiently. The parenthesized tool inventories for each pack are long but earn their space by letting the agent choose without a discovery round-trip; a slightly tighter listing would push this to a 5.

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?

There is no output schema, yet the description inlines the full return shape including per-pack/domain already_listed and list_changed flags. Combined with the session-lifetime, refresh, idempotency, and unknown-name error notes, nothing an agent needs in order to call this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and both parameters are enumerated, so the schema carries the identifiers. The description still adds meaningful semantics the enum cannot: it spells out which tools each pack contains, and warns that a domain 'can add a hundred tools to your context', which is genuine cost information for the caller.

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 ('adds packs or whole domains to this connection's tool list') and immediately contrasts the effect with the sibling path ('called directly instead of through call_tool'). An agent can distinguish it from call_tool and find_tools without opening any 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?

Gives explicit selection criteria: use a pack for a single job, a domain for a whole editor area, and 'Prefer a pack when one covers the job' resolves the tradeoff. It also points at the discovery alternative ('find_tools with no arguments lists the domains and their sizes') and states that packs, domains, or both are acceptable inputs.

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