blender-compact-mcp

by mohakmalviya

Overview Schema Source Related Servers Discussions Admin

Python

Local

inspect

Read a bounded Blender scene summary; pass object names to retrieve detailed properties.

Instructions

Read a bounded scene summary; pass names for detailed object properties.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`names`	No
`offset`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv0.2.1Oct 14, 2026
- removedInput schema / properties / limit / title
```
Removed value: -"Limit"
```
- removedInput schema / properties / names / anyOf
```
Removed value: -[
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / names / default
```
Removed value: -null
```
- addedInput schema / properties / names / items
```
Added value: +{
+  "type": "string"
+}
```
- removedInput schema / properties / names / title
```
Removed value: -"Names"
```
- addedInput schema / properties / names / type
```
Added value: +"array"
```
- removedInput schema / properties / offset / title
```
Removed value: -"Offset"
```
- removedInput schema / title
```
Removed value: -"inspectArguments"
```
First observedv0.2.0Sep 9, 2026

TDQS

B3/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. 'Read' implies non-mutation, but it says nothing about permissions, error behavior, cost, or what 'bounded' actually constrains.

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 tight sentence, front-loaded with the primary action, with the secondary mode in the following clause. No filler.

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

Completeness2/5

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

An output schema exists, so return values need no explanation, but with zero annotation coverage and three fully undocumented parameters the description is too thin for correct invocation — pagination, bounding, and failure modes are all missing.

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 coverage is 0%, so the description must compensate. It explains only 'names' (detailed object properties); 'limit' and 'offset' are never addressed beyond the vague word 'bounded', leaving pagination semantics undocumented.

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?

States a specific verb (read) and resource (bounded scene summary), plus a second mode via names. It reasonably separates itself from discover/execute/capture as the read/inspect tool, though 'scene summary' is domain jargon left undefined.

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?

Implies two modes — default bounded summary vs. detailed properties when names are passed — but gives no guidance on when to prefer this over siblings like discover, and no exclusions or prerequisites.

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

Deploy Server