Skip to main content
Glama

list_render_profiles

Lists available Blender render profiles and flags bounded profiles, real layers, and unsupported anatomy, helping you choose a valid setup without changing physics.

Instructions

Discover bounded Blender profiles, real layers and unsupported anatomy; physics remains unchanged.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.1

TDQS

C2.5/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. The phrase "physics remains unchanged" faintly implies a read-only, observation-only operation, but the claim is oblique and doesn't state side effects, permissions, or scope of the listing.

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?

One short, front-loaded sentence with no filler, but its compactness comes at the cost of clarity — the dense jargon-packed clause forces the agent to decode rather than understand.

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 and there are no parameters, so the description needn't explain return values. It remains under-complete in explaining what "bounded Blender profiles" are or what "real layers" and "unsupported anatomy" refer to within the result.

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 takes zero parameters, so there is nothing for the description to disambiguate. Baseline 4 applies; the description doesn't need to compensate for any schema gap.

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

Purpose2/5

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

"Discover ... Blender profiles" echoes the tool name's own verb+resource but adds cryptic qualifiers ("bounded", "real layers", "unsupported anatomy") that don't tell an agent what a render profile actually is or what the listing contains. Nothing distinguishes this from siblings like list_models or list_scenarios beyond the word "Blender".

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?

The description gives no when-to-use guidance, no prerequisites, and does not name any alternative tool. An agent has no signal for choosing list_render_profiles over list_models or describe_model.

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