Skip to main content
Glama

delete_light

Remove a named light object from a Blender scene, with optional confirmation to prevent accidental deletion.

Instructions

Delete a light object.

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": {
      "name": "<name>"
    },
    "name": "delete_light"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
confirmedNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden for a destructive operation and discloses almost nothing: it does not say whether deletion is permanent, undoable, blocked when the light is in use, or gated behind the `confirmed` flag. Only the mutation intent is communicated via the verb "delete".

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with zero waste, so structure is fine, but it is terse to the point of under-specification rather than genuinely optimized. Nothing is front-loaded beyond the bare verb-resource pair.

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

Completeness2/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 not be explained, but for a destructive two-parameter tool with no annotations the description should at minimum explain the `confirmed` guard and the identifier semantics. Neither is present, leaving the agent unable to predict the tool's safety behavior.

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

Parameters1/5

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

Schema description coverage is 0% for both parameters, so the description must compensate, and it adds nothing about `name` (identifier format, case sensitivity, whether it refers to a datablock vs a scene object) or `confirmed` (apparently a destructive-action guard whose default false is significant). This is the most serious gap for an agent trying to call the tool correctly.

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?

A specific verb plus resource ("Delete a light object"), which reads clearly and is distinguishable from create_light/modify_light. It does not differentiate itself from the other delete_* siblings (delete_object, delete_geometry, delete_collection), so the agent must infer that this one targets light datablocks specifically.

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

Usage Guidelines2/5

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

No when-to-use guidance, no prerequisites, and no mention of when to prefer this over delete_object or delete_objects. The agent is left to infer selection context (e.g., whether the light must be active/selected) entirely on its own.

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

Deploy Server

Other Tools