Skip to main content
Glama

blender_health

Read-only

Check Blender's live session status by reading its session ID, open file, scene, version, and Python availability to confirm the connection is ready before running commands.

Instructions

Read Blender's live session ID, file, scene, version and Python availability.

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

Input Schema

NameRequiredDescriptionDefault
timeoutNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

B3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safe-read profile is covered. The description adds the useful detail of what state is observed (session ID, file, scene, version, Python availability), but omits the behavior that matters most for a health probe: whether it errors or returns an unhealthy status when Blender is not running, and how the timeout parameter affects that.

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?

One front-loaded sentence of about thirteen words with no filler or redundancy. It is efficient, though its terseness is part of why usage and timeout behavior go unaddressed.

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?

An output schema exists, so return-value structure need not be explained. However, for a tool whose evident role is gating other Blender calls, the missing failure/unhealthy semantics and the undocumented timeout leave a meaningful gap for an agent deciding whether it can trust a negative result.

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?

Schema description coverage is 0%, so the single timeout parameter (default 3) is documented nowhere in structured form and the description never mentions it. It neither explains units (seconds), nor what happens on expiry, leaving the one parameter's semantics entirely unstated.

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 specific verb (Read) plus a concrete list of resources retrieved: live session ID, file, scene, version, and Python availability. That is clearly distinguishable from execution or inspection siblings like execute_blender_code or inspect_rig, though it never names a sibling explicitly.

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?

There is no when-to-use guidance, no mention of prerequisites, and no routing to or away from alternatives. An agent must infer that this is a pre-flight connectivity/status check before calling execution tools; nothing in the text says so.

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