Skip to main content
Glama
pzfreo

build123d-mcp

by pzfreo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

view_axes

Read-only

Check world-to-page axis mapping before rendering a projected view to catch axis swaps and sign flips, computed analytically without projection.

Instructions

DEPRECATED (#465) — moved to draftwright; off by default in 0.4.0, removed in 0.5.0. Calling it explains the replacement. Return the world→page axis mapping for a project_to_viewport call, computed analytically (no projection performed). Use this BEFORE rendering a projected view to confirm which world axis ends up on which page axis and with what sign — catches bottom-view/side-view axis swaps before they show up in the render.

Returns JSON like {"world_X": ["page_X", -1.0], "world_Y": ["page_Y", 1.0],
"world_Z": ["depth", 0.0]} — for a bottom-view origin (0,0,-100), world-X
flips to negative page-X.

Args:
    viewport_origin: camera position, same arg as project_to_viewport.
    viewport_up: up vector. Defaults to (0,1,0).
    look_at: target point. Defaults to origin.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
look_atNo
viewport_upNo
viewport_originYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.3.42
    • addedInput schema / properties / look_at / anyOf
      Added value: +[
+  {
+    "items": {
+      "type": "number"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / look_at / default
      Previous value: -[
-  0,
-  0,
-  0
-]New value: +null
    • removedInput schema / properties / look_at / items
      Removed value: -{
-  "type": "number"
-}
    • removedInput schema / properties / look_at / type
      Removed value: -"array"
    • addedInput schema / properties / viewport_up / anyOf
      Added value: +[
+  {
+    "items": {
+      "type": "number"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / viewport_up / default
      Previous value: -[
-  0,
-  1,
-  0
-]New value: +null
    • removedInput schema / properties / viewport_up / items
      Removed value: -{
-  "type": "number"
-}
    • removedInput schema / properties / viewport_up / type
      Removed value: -"array"
  2. Addedv0.3.27

TDQS

A5/5.0
Behavior5/5

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

Even though readOnlyHint is already set, the description adds substantial behavioral detail: it is computed analytically, performs no projection, is deprecated/off/removed in specific versions, and returns a JSON mapping with a concrete sign-flip example. This goes well beyond the annotation.

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 dense but well-organized: deprecation status is front-loaded, followed by purpose, usage timing, example output, and parameter explanations. Each section earns its place and nothing feels redundant.

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

Completeness5/5

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

For a read-only analytical tool, the description is complete: it covers when to use it, what it returns, how the return is structured, the meaning of each parameter, and the deprecation behavior. The output schema also exists, so return values are fully covered.

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

Parameters5/5

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

Schema description coverage is 0%, and the description compensates fully for all three parameters: viewport_origin is the camera position and same arg as project_to_viewport, viewport_up is the up vector defaulting to (0,1,0), and look_at is the target point defaulting to origin. This adds real meaning absent from 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 states a specific verb and resource: it returns the world→page axis mapping for a project_to_viewport call, computed analytically with no projection performed. This clearly separates it from rendering tools and explains its role in catching axis swaps.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says to use this BEFORE rendering a projected view, and explains that it catches bottom-view/side-view axis swaps. It also gives a clear when-not via the deprecation notice and names the replacement (draftwright), plus notes that calling it explains the replacement.

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

Deploy Server

Other Tools