mcp-printable

Overview Schema Source Related Servers Discussions Admin

blender_check_clearance_sweep

Read-onlyIdempotent

Rotates inner object 360° to detect collisions and return worst-case clearance for hinges, joints, and articulating mechanisms.

Instructions

Rotate inner_object through 360° and check clearance at each step. MANDATORY for any joint, hinge, or articulating mechanism.

A hinge that looks fine at 0° may collide at 90°. Returns worst-case clearance and the angle where it occurs. passes=False → the joint WILL fuse during printing.

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": {
      "inner_object": "<inner_object>",
      "outer_object": "<outer_object>"
    },
    "name": "blender_check_clearance_sweep"
  }
}

Input Schema

Name	Required	Default
`axis`	No	Z
`steps`	No
`inner_object`	Yes
`outer_object`	Yes
`min_clearance_mm`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.3Aug 9, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare read-only and non-destructive behavior, and the description adds behavioral context beyond this: it rotates the object, checks each step, returns worst-case clearance and the angle, and explains that passes=False means the joint WILL fuse. This enriches the agent's understanding of the simulation without contradicting the annotations.

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?

The description is succinct and well-structured. It starts with the core action, states when it's mandatory, provides a concrete illustrative example, and ends with the output significance. Every sentence earns its place without redundancy.

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

Completeness4/5

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

Given the presence of an output schema (which likely documents the return fields) and rich annotations, the description covers the essential usage context, including the importance of the sweep and the interpretation of passes=False. It does not mention the axis parameter or the min_clearance_mm threshold explicitly, but the overall description is sufficient for an agent to select and invoke the tool correctly in most scenarios.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description has to explain the parameters. It clarifies inner_object (the one rotated), outer_object (implicitly the obstacle), steps (each step of rotation), and implies min_clearance_mm via the pass/fail threshold. However, it does not explicitly define min_clearance_mm or the axis parameter, so the agent must infer their exact meaning from context or the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool rotates inner_object through 360° and checks clearance at each step, specifying both the action and the objects involved. It distinguishes itself from the sibling blender_check_clearance by adding 'sweep' and emphasizing rotation around a full circle, making it unique for articulating mechanisms.

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?

The description says it is MANDATORY for any joint, hinge, or articulating mechanism, and provides a concrete example (a hinge may collide at 90°). This gives clear when-to-use guidance, but it does not explicitly mention when not to use it or name an alternative tool like blender_check_clearance for static checks, so it stops short of a full 5.

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