Skip to main content
Glama

get_environment

Retrieve actual Blender/Python versions, enabled add-ons, devices, and GUI capabilities for a session to verify remote environment compatibility.

Instructions

Inspect actual Blender/Python versions, enabled add-ons, devices and GUI capabilities.

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

Input Schema

NameRequiredDescriptionDefault
session_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It usefully discloses what information is exposed (versions, add-ons, devices, GUI capabilities), but says nothing about whether it is read-only, what happens with an invalid session, whether it is expensive, or how results are shaped.

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 with no filler, and the enumerated capabilities are packed efficiently into one clause. Nothing could be trimmed without losing content.

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 one-parameter introspection tool with no output schema, the description covers the domain of returned information at a category level, which is reasonably adequate. It still leaves the parameter meaning, error behavior, and return structure unspecified, so it is only minimally complete.

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%, and the description never mentions session_id, the sole parameter. The agent must guess whether it is a live Blender session identifier and what happens if it is stale; the job of compensating for the uncovered schema is left undone.

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 gives a specific verb (Inspect) and enumerates the resource contents it covers: Blender/Python versions, enabled add-ons, devices, and GUI capabilities. That makes the tool's scope distinguishable from siblings like inspect_scene or inspect_dependencies, though it never explicitly contrasts itself with them.

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?

There is no statement of when to call this versus alternatives such as session_status, get_logs, or inspect_dependencies, and no prerequisites or exclusions are given. The word 'actual' faintly hints at verifying real runtime state, but the agent must infer the use case.

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