Skip to main content
Glama

Render Capabilities

render_capabilities
Read-only

Discover which photoreal renderers are usable now, including Blender and FreeCAD Render add-ons, and get install instructions for missing ones to avoid guesswork.

Instructions

Report which photoreal renderers are usable right now — Blender (the studio backend) and the FreeCAD Render add-on renderers — so you can pick one for render_photoreal, or tell the user exactly what to install, instead of discovering availability by trial and error.

Takes no arguments and renders nothing. Resolves Blender like a solver (ANKUSDRIVE_BLENDER_PATH -> PATH -> per-OS install dirs, incl. the versioned Blender Foundation\Blender X.Y and /opt|~/.local/opt/blender-*) and launches it once (cached) to read its version and GPU; resolves each add-on renderer as render_photoreal would, changing no settings.

Returns {default_renderer ('auto'), auto_selects (the renderer 'auto' would use now, or None), recommended ('Blender'), platform, available (ready renderer names for renderer=), renderers: {name: {available, backend ('blender' | 'render_addon'), path or install_hint, ...}} — Blender adds version, device, gpu, oidn, supported, scenes, qualities, devices, finishes — materials (appearance card names), appearance_fields (the PBR dict keys), addon_importable, addon_error (when the add-on does not import), and suggestion {renderer, why, install} while Blender is missing}. When the user wants better renders, relay the Blender install_hint verbatim — never run installers yourself. setup_status reports the same install under the studio_render family.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only say readOnlyHint=true and openWorldHint=false, but the description adds meaningful behavioral detail: it 'Takes no arguments and renders nothing,' 'launches [Blender] once (cached),' 'changing no settings,' and 'never run installers yourself.' This is essential context beyond the annotations and there is no contradiction.

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

Conciseness5/5

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

The description is long but every sentence earns its place: purpose, side-effect behavior, resolution logic, return structure, usage caution, and sibling relationship are all covered. It is front-loaded with the primary purpose and contains no wasted filler.

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?

There is no output schema, yet the description supplies a detailed return contract including default_renderer, auto_selects, recommended, available, renderers, Blender-specific fields, addon_error, and suggestion. It also covers edge cases like missing Blender and the install_hint, making the tool fully usable without external documentation.

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

Parameters4/5

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

The tool has zero parameters and the input schema is empty with 100% coverage, so there is no parameter semantics to add. The description explicitly states 'Takes no arguments,' which makes the parameter situation unambiguous. The baseline of 4 is appropriate for a no-parameter tool.

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 opens with a specific verb and resource: 'Report which photoreal renderers are usable right now.' It clearly distinguishes itself from render_photoreal by framing the tool as the way to pick a renderer before calling it, rather than discovering availability by trial and error.

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 explicitly says when to use this tool: 'so you can pick one for render_photoreal, or tell the user exactly what to install.' It also gives an exclusion ('never run installers yourself') and points to a sibling relationship with setup_status for install reporting.

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