Skip to main content
Glama

get_logs

Reads the tail of Blender's native log to surface errors missing from Python stdout, helping diagnose remote session issues.

Instructions

Read the tail of Blender's native log for errors not captured in Python stdout.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "session_id": "<session_id>"
    },
    "name": "get_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_bytesNo
session_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the key traits: this is a read of the native Blender log (not Python output) and it returns only the tail. It omits what happens when the log is missing or rotated, whether reads are per-session, and how truncation is surfaced, so an agent cannot fully predict the result.

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?

A single front-loaded sentence that identifies the target, the mechanism, and the use case with no wasted wording. Nothing needs trimming or reordering.

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?

For a two-parameter read tool with no output schema this is close to sufficient, since the return value (log text) is implied by 'read the tail'. However, the unexplained max_bytes parameter and the unstated behavior when no log exists leave real gaps for reliable invocation.

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% for both parameters, and the description mentions neither session_id nor max_bytes. The word 'tail' hints that output size is bounded, but the meaning and default of max_bytes (a 1-64000 cap) is never explained, leaving the description to fall short of the compensation the low coverage requires.

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 names a specific verb and resource ('Read the tail of Blender's native log') and scopes it to errors that Python stdout misses, which separates it from execute_python or job output tools. It stops short of naming a sibling outright, so it is clear but not maximally differentiated.

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

Usage Guidelines4/5

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

'for errors not captured in Python stdout' gives a concrete condition that tells an agent when this tool is the right choice. There are no explicit exclusions or named alternatives, which is the only thing keeping it below a 5.

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