Skip to main content
Glama
Vectorworks MCP

Vectorworks MCP

vw_point_to_world

Read-only

Convert a pixel from the last mapped screenshot into Vectorworks drawing coordinates so you can locate pictured objects or verify placements.

Instructions

Turn a pixel of the last mapped screenshot into drawing coordinates.

Pure arithmetic, no job, read-only. Use it to say where something seen in the picture is, such as the gap a truss should fill, or to check that an object landed where it looks. Needs a prior vw_screenshot(mapping=True). Exact in Top/Plan views only; otherwise the result carries a warning. Returns {x, y, units, warning?}.

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": {
      "px": "<px>",
      "py": "<py>"
    },
    "name": "vw_point_to_world"
  }
}

Input Schema

NameRequiredDescriptionDefault
pxYesPixel x in the screenshot image, from its left edge.
pyYesPixel y in the screenshot image, from its top edge.
mappingNoThe `mapping` dict returned by an earlier vw_screenshot(mapping=True). Default: the most recent one in this server session.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.1
    • addedInput schema / properties / mapping / description
      Added value: +"The `mapping` dict returned by an earlier vw_screenshot(mapping=True). Default: the most recent one in this server session."
    • addedInput schema / properties / px / description
      Added value: +"Pixel x in the screenshot image, from its left edge."
    • addedInput schema / properties / py / description
      Added value: +"Pixel y in the screenshot image, from its top edge."
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and openWorldHint=false, and the description adds real value on top: 'Pure arithmetic, no job, read-only' clarifies no document mutation or job execution occurs, the prerequisite screenshot dependency is disclosed, and the accuracy limitation in non-orthographic views is stated with the mitigation (a warning in the result). This is exactly the kind of behavioral context annotations cannot carry.

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?

Front-loaded with the core operation, then purpose, then prerequisites, then the return shape — four short sentences with zero filler. Every sentence earns its place and the constraint order matches how an agent would plan the call.

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?

For a three-parameter, no-output-schema tool, the description supplies the return shape ({x, y, units, warning?}), the prerequisite, and the precision caveat. Minor gaps remain: it does not explain what 'units' resolves to (document units vs. page units) or what happens on invalid pixel input, but nothing critical to calling it correctly is missing.

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 100%, so px, py, and mapping are all documented in the schema itself; the description only restates the provenance of the mapping argument ('Needs a prior vw_screenshot(mapping=True)'). It adds no coordinate-system, unit, or rounding details beyond the schema, so the baseline of 3 applies.

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?

States a precise verb and resource: 'Turn a pixel of the last mapped screenshot into drawing coordinates.' An agent immediately knows the input (pixel) and the output (drawing coordinates), and the follow-up sentences reinforce the concrete use cases (locating a truss gap, verifying placement).

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?

Gives explicit when-to-use cases ('say where something seen in the picture is', 'check that an object landed where it looks'), a hard prerequisite ('Needs a prior vw_screenshot(mapping=True)'), and a when-not/boundary condition ('Exact in Top/Plan views only; otherwise the result carries a warning'). It stops short of naming an alternative route for non-Top/Plan views, so it is strong rather than complete.

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