blender-mcp

blender_logs

View recent Blender log entries with filters for level, module, and time range, or get log statistics including total entries and level distribution.

View recent logs or log buffer statistics (portmanteau).

Operations:

view: Recent log entries with optional filters (level_filter, module_filter, limit, since_minutes, include_details)
stats: Log buffer statistics (total entries, time range, level distribution)

TableJSON Schema

Name	Required	Description	Default
`operation`	No	One of view, stats	view
`level_filter`	No	For view - DEBUG, INFO, WARNING, ERROR, CRITICAL
`module_filter`	No	For view - partial module name match
`limit`	No	For view - max entries (1-100)
`since_minutes`	No	For view - logs from last N minutes
`include_details`	No	For view - include function/line in output

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

A3.9/5.0

Behavior3/5

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

Without annotations, the description implies read-only behavior but doesn't explicitly state safety or side effects.

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?

Concise with clear operation breakdown, though the word 'portmanteau' is unnecessary.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description adequately covers the tool's functionality and parameters.

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 description maps parameters to specific operations, adding value beyond the schema's per-parameter descriptions.

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 clearly states the tool views logs or gets buffer statistics, distinguishing it from sibling tools that focus on 3D operations.

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

Usage Guidelines3/5

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

No explicit guidance on when to use this tool vs alternatives, but the operations are self-explanatory.

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

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sandraschi/blender-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server