Skip to main content
Glama
Sign In
blender-mcp

blender-mcp

by sandraschi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

blender_logs

Read-onlyIdempotent

Access Blender logs to troubleshoot issues. View filtered recent entries or retrieve buffer statistics for monitoring and diagnostics.

Instructions

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)

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_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoFor view - max entries (1-100)
operationNoOne of view, statsview
level_filterNoFor view - DEBUG, INFO, WARNING, ERROR, CRITICAL
module_filterNoFor view - partial module name match
since_minutesNoFor view - logs from last N minutes
include_detailsNoFor view - include function/line in output

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds operational behavior by describing what each operation does, including the stats output (total entries, time range, level distribution), which goes beyond the annotations without contradicting them.

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 compact, starting with a clear one-sentence purpose and using a bulleted list for operations. Every sentence contributes meaning, with no unnecessary filler.

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?

Given the read-only nature, full schema coverage, and presence of an output schema, the description sufficiently explains the tool's functionality and parameter applicability. It does not discuss limitations or integration details, but these are not critical for a well-annotated read-only log tool.

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 input schema has 100% parameter description coverage, so baseline is 3. The description adds value by explicitly grouping parameters under 'view' and 'stats', clarifying which parameters apply to which operation and what the stats operation returns, which the schema does not fully convey.

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 'View recent logs or log buffer statistics' with a specific verb and resource. It then details two distinct operations (view and stats), making the tool's purpose unambiguous and distinguishable from sibling tools like show_logs_app.

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?

The description provides operation-specific parameter groupings (view vs stats) but does not explicitly state when to use this tool instead of siblings such as show_logs_app or blender_status. There are no alternative/exclusion statements, so guidance is only implied.

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