Skip to main content
Glama

open

Launches an application outside the caller's container and waits for its agent, returning selector, PID, mode, version, and startup time.

Instructions

Starts the app outside the caller's container and waits for its agent. Returns: selector, pid, mode, version, startup_s (seconds). Blender: background=True is a headless daemon: the factory scene (cube, camera, light), no user settings and no add-ons unless addons=['Name', ...] (add-on module names) or the TETHER_ADDONS environment variable are given; it closes after 30 minutes idle or when this session ends. background=False is windowed: it starts with the user's settings and the splash window shows. file = a .blend to load at startup; clean = start without user settings.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "app": "<app>"
    },
    "name": "open"
  }
}

Input Schema

NameRequiredDescriptionDefault
appYes
fileNo
cleanNo
addonsNo
backgroundNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, destructiveHint=false, openWorldHint=false; the description adds substantive behavior beyond that: startup happens outside the caller's container, the call blocks waiting for the agent, and the headless daemon closes after 30 minutes idle or at session end. It also discloses that windowed mode loads user settings and shows the splash window. Gaps remain on error handling and whether an existing session is terminated, but the disclosure is well above the annotation baseline.

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 return values are front-loaded in the first sentence, and the mode semantics follow in a logical order. The Blender paragraph is dense and slightly run-on, but every sentence conveys operational information rather than filler.

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

Completeness3/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 usefully names the returned fields, and it covers lifecycle and cleanup behavior for a stateful launch tool. However, the required app parameter is undefined, only Blender's behavior is documented, and nothing is said about failure modes or invalid app values.

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 0%, so the description must carry all parameter meaning, and it covers background, file, clean, and addons in useful detail, including a concrete addons list format. Critically, the single required parameter, app, is never described at all — the agent is not told it is an application name or which values are accepted. Partial compensation only.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a concrete verb and effect: "Starts the app outside the caller's container and waits for its agent," and it even enumerates the return fields (selector, pid, mode, version, startup_s). That is far more specific than the bare name "open." It does not, however, contrast itself with siblings such as run, generate_start, or status, so the agent must infer the distinction.

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

Usage Guidelines3/5

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

The description explains the choice between background=True (headless daemon) and background=False (windowed), plus how file, clean, and addons modify startup, which is real in-tool guidance. It never states when to call open rather than run, generate_start, or status, nor whether open must precede run or what happens if a session is already open. Usage is implied rather than directed.

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