inspect_voxel_modelInspect a temporary VoxelDraft modelRef. Returns voxel count, command count, bounds, and colors.
| Name | Required | Description | Default |
|---|---|---|---|
| modelRef | Yes | Short temporary VoxelDraft model reference returned by model tools |
Changes observed during successful MCP inspections.
Input schema / properties / modelRef / descriptionPrevious value: -"Short temporary VoxelDraft model reference that expires after 7 days of inactivity"New value: +"Short temporary VoxelDraft model reference returned by model tools"Output schema / (root)Previous value: -{
- "additionalProperties": false,
- "properties": {
- "name": {
- "type": "string"
- },
- "palette": {
- "items": {
- "pattern": "^#[0-9a-fA-F]{6}$",
- "type": "string"
- },
- "maxItems": 64,
- "type": "array"
- },
- "stats": {
- "additionalProperties": false,
- "properties": {
- "bounds": {
- "anyOf": [
- {
- "type": "null"
- },
- {
- "additionalProperties": false,
- "properties": {
- "max": {
- "items": {
- "maximum": 63,
- "minimum": 0,
- "type": "integer"
- },
- "maxItems": 3,
- "minItems": 3,
- "type": "array"
- },
- "min": {
- "items": {
- "maximum": 63,
- "minimum": 0,
- "type": "integer"
- },
- "maxItems": 3,
- "minItems": 3,
- "type": "array"
- },
- "size": {
- "items": {
- "maximum": 64,
- "minimum": 1,
- "type": "integer"
- },
- "maxItems": 3,
- "minItems": 3,
- "type": "array"
- }
- },
- "required": [
- "min",
- "max",
- "size"
- ],
- "type": "object"
- }
- ]
- },
- "colors": {
- "items": {
- "pattern": "^#[0-9a-fA-F]{6}$",
- "type": "string"
- },
- "maxItems": 512,
- "type": "array"
- },
- "commandCount": {
- "maximum": 512,
- "minimum": 0,
- "type": "integer"
- },
- "voxelCount": {
- "maximum": 100000,
- "minimum": 0,
- "type": "integer"
- }
- },
- "required": [
- "voxelCount",
- "commandCount",
- "colors",
- "bounds"
- ],
- "type": "object"
- }
- },
- "required": [
- "name",
- "palette",
- "stats"
- ],
- "type": "object"
-}New value: +nullInput schema / properties / modelRemoved value: -{
- "type": "string"
-}Input schema / properties / modelRefAdded value: +{
+ "description": "Short temporary VoxelDraft model reference that expires after 7 days of inactivity",
+ "maxLength": 64,
+ "type": "string"
+}Input schema / requiredPrevious value: -[
- "model"
-]New value: +[
+ "modelRef"
+]Output schema / (root)Previous value: -nullNew value: +{
+ "additionalProperties": false,
+ "properties": {
+ "name": {
+ "type": "string"
+ },
+ "palette": {
+ "items": {
+ "pattern": "^#[0-9a-fA-F]{6}$",
+ "type": "string"
+ },
+ "maxItems": 64,
+ "type": "array"
+ },
+ "stats": {
+ "additionalProperties": false,
+ "properties": {
+ "bounds": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "additionalProperties": false,
+ "properties": {
+ "max": {
+ "items": {
+ "maximum": 63,
+ "minimum": 0,
+ "type": "integer"
+ },
+ "maxItems": 3,
+ "minItems": 3,
+ "type": "array"
+ },
+ "min": {
+ "items": {
+ "maximum": 63,
+ "minimum": 0,
+ "type": "integer"
+ },
+ "maxItems": 3,
+ "minItems": 3,
+ "type": "array"
+ },
+ "size": {
+ "items": {
+ "maximum": 64,
+ "minimum": 1,
+ "type": "integer"
+ },
+ "maxItems": 3,
+ "minItems": 3,
+ "type": "array"
+ }
+ },
+ "required": [
+ "min",
+ "max",
+ "size"
+ ],
+ "type": "object"
+ }
+ ]
+ },
+ "colors": {
+ "items": {
+ "pattern": "^#[0-9a-fA-F]{6}$",
+ "type": "string"
+ },
+ "maxItems": 512,
+ "type": "array"
+ },
+ "commandCount": {
+ "maximum": 512,
+ "minimum": 0,
+ "type": "integer"
+ },
+ "voxelCount": {
+ "maximum": 100000,
+ "minimum": 0,
+ "type": "integer"
+ }
+ },
+ "required": [
+ "voxelCount",
+ "commandCount",
+ "colors",
+ "bounds"
+ ],
+ "type": "object"
+ }
+ },
+ "required": [
+ "name",
+ "palette",
+ "stats"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, which is the notable fact here: an 'Inspect' tool that returns counts is framed as a read, yet it is explicitly not marked read-only. The description never explains what non-read-only effect occurs (e.g., keeping the temporary draft alive or locking it), so the safety profile the agent gets is only partially consistent with the tool's framing.
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 tight sentences, zero waste, with the read purpose front-loaded and the return payload enumerated immediately after. Nothing needs trimming or reordering.
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 one-parameter, no-output-schema tool, the description covers the operation and its return contents well. The remaining gap is the unexplained non-read-only annotation and any permission/lifetime caveats on the temporary model.
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?
There is a single parameter with 100% schema description coverage, and the schema already explains it as a short temporary VoxelDraft reference. The description adds nothing beyond that baseline, so 3 is appropriate.
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 (Inspect) and resource (temporary VoxelDraft modelRef), and even names the payload it produces (voxel count, command count, bounds, colors). It does not, however, distinguish itself from siblings like render_voxel_model or list_voxel_projects, so an agent must infer the boundary.
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?
There is no explicit when-to-use, when-not-to-use, or alternative routing. The only contextual clue is that the modelRef is a 'short temporary reference returned by model tools,' which weakly implies inspection after model generation, but that is inference rather than guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.