Skip to main content
Glama

inspect_spatial_pairs

Read-only

Measure distances between evaluated mesh pairs in Blender world space, optionally over frames, and request SVG witness diagrams for spatial inspection.

Instructions

Measure evaluated mesh pairs in world space, optionally over frames and with witness diagrams.

Use current-frame live inspection by default or open a specified blend file in background Blender. Supply frames or frame_range (start, end, step) for subframes. Distances and tolerance are in Blender units. Request front, side, top or isometric SVG evidence at one sampled frame. The query restores the original frame.

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": {
      "pairs": "<pairs>"
    },
    "name": "inspect_spatial_pairs"
  }
}

Input Schema

NameRequiredDescriptionDefault
pairsYes
viewsNo
framesNo
timeoutNo
toleranceNo
blend_fileNo
frame_rangeNo
evidence_frameNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the query temporarily changes frame but 'restores the original frame', and it can operate in background Blender with a timeout. It omits cost/runtime expectations for multi-frame sweeps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Dense but front-loaded: the core action comes first, then mode selection, then units and evidence options. The broken line wrapping and sentence fragments are stylistic noise rather than wasted content, and nothing is obviously redundant.

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?

With an output schema present, return values need not be explained, and the description covers modes, units, frame restoration, and evidence generation. The remaining gap is the unexplained structure of the required pairs argument for an 8-parameter tool with zero schema documentation.

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?

Schema description coverage is 0%, so the description carries the full burden across 8 parameters. It successfully clarifies frame_range as (start, end, step), states tolerance is in Blender units, and lists the valid view kinds (front, side, top, isometric) and that evidence is taken at one sampled frame. It says nothing about the required 'pairs' argument's element structure or the timeout parameter, leaving meaningful gaps.

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 names a specific verb and resource — 'Measure evaluated mesh pairs in world space' — plus the optional extensions (frame sweeps, witness diagrams). It is clearly distinguishable from siblings like inspect_rig or inspect_clothing_fit, though it never names an alternative tool explicitly.

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?

It does explain the two operating modes ('current-frame live inspection by default or open a specified blend file in background Blender') and how to request subframe sampling, which is real usage context. It gives no when-not-to-use guidance and no routing to sibling tools, so an agent must infer the boundary on its own.

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