Skip to main content
Glama

close

Destructive

Terminate only a background Blender agent session. To shut a window opened via open, call bpy.ops.wm.quit_blender() through run; a dropped connection is not an error.

Instructions

Closes only a background agent. The user closes a windowed Blender; close a window you opened with open only by calling bpy.ops.wm.quit_blender() through run (the connection drops, which is not counted as an error).

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

Input Schema

NameRequiredDescriptionDefault
appYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already flag destructive=true and readOnly=false, but the description adds behavior annotations cannot express: the tool is limited to background agents, and the connection dropping during the quit_blender path is explicitly not an error. That last clause prevents an agent from misreading a normal disconnect as a failure, which is high-value operational context.

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?

Two sentences with no filler, and the scoping restriction is front-loaded. The second sentence is dense with two parenthetical asides and a run-on structure, which slightly taxes first-pass parsing, but every clause carries real information.

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 prose, and the tool has only one parameter and one action. The description covers the non-obvious parts an agent could get wrong: background-only scope, the correct alternative for windowed sessions, and the benign connection drop.

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

Parameters2/5

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

There is one required parameter (app) with 0% schema description coverage, so the description carries the full burden of explaining it, and it never mentions the parameter or what value it takes. The reference to "a background agent" hints that app identifies the agent, but format, expected values, and behavior on an unknown app are left entirely undocumented.

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?

"Closes only a background agent" gives a specific verb plus an explicit scope restriction, which is exactly what distinguishes it from run (quit_blender) and from the user closing a window. An agent can tell what this does and what it does not do without consulting any other field.

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?

The description states both when to use it (background agents) and when not to (windowed Blender, which the user closes themselves), and names the alternative path for windows it opened via open: bpy.ops.wm.quit_blender() through run. Alternatives and exclusions are explicit rather than implied.

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