Skip to main content
Glama

manage_extensions

Destructive

List, enable, or disable Omniverse Kit extensions in a running app to add needed capabilities or diagnose extension-dependent tools.

Instructions

List the Kit app's extensions, or turn one on or off in the running app.

"list" (the default) only reads: each extension's id, version and whether it is on, the first 50 shown with the total. "enable" and "disable" need extension_id, last until Kit restarts, and answer whether the extension is on afterwards: enabled=False after an enable means it didn't take. Use enable when a tool names an extension it lacks, such as omni.syntheticdata for segmentation. Disabling one that other tools use breaks them, and disabling ovmcp.bridge cuts this server off from Kit.

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": "manage_extensions"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionNo"list" reads; "enable" and "disable" change the running applist
searchNoFor "list": only extensions whose name or id contains this, in any case
enabled_onlyNoFor "list": only enabled extensions
extension_idNoFor "enable" and "disable", required: the extension, e.g. "omni.syntheticdata"

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.3
    • changedInput schema / properties / action / description
      Previous value: -"What to do"New value: +"\"list\" reads; \"enable\" and \"disable\" change the running app"
    • changedInput schema / properties / extension_id / description
      Previous value: -"The extension to enable or disable"New value: +"For \"enable\" and \"disable\", required: the extension, e.g. \"omni.syntheticdata\""
    • changedInput schema / properties / search / description
      Previous value: -"For \"list\": only extensions whose name contains this"New value: +"For \"list\": only extensions whose name or id contains this, in any case"
  2. First observedv0.2.2

TDQS

A4.6/5.0
Behavior5/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, and the description substantiates exactly why: enable/disable mutate the running app, persist only until Kit restarts, and can break other tools or cut off the MCP bridge. It also discloses the response semantics (enabled=False after an enable means it didn't take) and the list truncation behavior (first 50 with the total), which annotations cannot convey.

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 purpose and default behavior come first, then the read path, then the mutation semantics and safety warnings, in a logical order. It is dense and slightly overlong, but nearly every clause (restart persistence, enabled=False signal, bridge warning) carries information an agent would otherwise have to infer.

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?

An output schema exists, so return values need no explanation, and the description still covers what the agent needs beyond it: the three modes, the required id for mutation, transient lifetime of changes, and the failure/breakage modes. For a 4-parameter tool with destructive semantics, nothing material 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%, so action, search, enabled_only, and extension_id are already fully documented with per-action applicability. The description reinforces that enable/disable need extension_id but adds no format or edge-case detail, and it never mentions the search or enabled_only filters, so it sits at the baseline for a fully-covered schema.

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?

The description names the specific resource (the Kit app's extensions) and the three concrete operations: list, enable, disable. It also states the default action, so an agent can distinguish the read path from the two mutation paths without opening the 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?

It gives an explicit trigger for enable ("Use enable when a tool names an extension it lacks, such as omni.syntheticdata for segmentation") and concrete when-not-to guidance for disable (disabling extensions other tools use breaks them; disabling ovmcp.bridge severs this server). That is when/when-not/alternative guidance in one place.

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