Verify Blender 5.2 availability, host OS, and knowledge readiness, returning JSON with binary paths and status so agents can confirm the runtime before generating 3D parts.
Inspect the host environment for Blender 5.2 availability, OS, and knowledge readiness.
Returns: JSON string describing Blender binary availability, paths, and status.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden; 'Inspect' implies a read-only probe but it never states that no host state is modified, nor any permission or cost implications. It does disclose what kind of data comes back (binary availability, paths, status), which partially compensates.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences, front-loaded with the purpose, with a separate Returns block. The Returns sentence largely restates what the output schema already declares, so it is slightly redundant but not harmful.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter read-only probe with an output schema, the description covers scope, target version (5.2), and the categories of information returned. The main gap is that it doesn't say when to call it or what 'knowledge readiness' concretely covers, but an agent has enough to invoke it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, which sets the baseline at 4, and the description correctly adds nothing about arguments, consistent with the empty schema. There is no parameter meaning left to clarify.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource: 'Inspect the host environment for Blender 5.2 availability, OS, and knowledge readiness', which clearly identifies this as an environment/preflight status probe rather than a validation or execution tool. It does not explicitly contrast itself with siblings like query_blender_knowledge, so it falls short of a 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The word 'Inspect' plus 'availability' and 'readiness' strongly implies a preflight check before calling execute_blender_pass, but the description never says so or names any alternative. Usage is inferable rather than explicit, which is the definition of a 3.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.