Skip to main content
Glama
nx-ai-bridge

nx-ai-bridge

by qiuyekai

screenshot

Captures and returns a PNG image of the NX graphics window so you can view the model, with optional fit and view orientation; available only in live mode.

Instructions

Save a PNG image of the NX graphics window so you can SEE the model. The MCP server returns the image itself. Only available in live mode (batch mode has no graphics window).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
fitNoFit the model to the window first.
pathNoAbsolute output path ending in .png. Auto-generated when omitted.
viewNoOrient the view before capturing; 'current' leaves the view untouched.isometric

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden; it does disclose the return channel (the image itself) and the live-mode requirement. It omits side effects: 'fit' and 'view' reorient the graphics window, so calling this mutates view state, and nothing is said about failure behavior if no window exists or the path is invalid.

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?

Three compact sentences with the core purpose front-loaded and the mode constraint placed after the main statement. There is little waste, though the 'so you can SEE the model' phrasing is slightly informal for a technical definition.

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-optional-parameter capture tool with no output schema, the definition covers what it produces (PNG returned in-band) and when it is available (live mode only). The remaining gap is side effects on the viewing state and error behavior, which for a simple read-only capture is a modest omission.

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 fit, path, and view are already fully documented, including the enum semantics for 'current'. The description adds no meaning beyond that, so the baseline of 3 applies.

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?

Specific verb and resource: 'Save a PNG image of the NX graphics window,' plus the useful clarification that the MCP server returns the image itself rather than a file handle. It does not explicitly differentiate from export_stl/export_step, which is the most likely confusion point for an agent choosing between raster capture and geometry export.

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 a hard eligibility rule: 'Only available in live mode (batch mode has no graphics window),' which prevents a whole class of failed calls. However, it never states when to prefer this over exporting geometry or other siblings, so an agent gets a precondition but no comparative routing advice.

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