Skip to main content
Glama
ldraw-mcp

ldraw-mcp

by musharna

render_ldraw_file

Renders LDraw model files (.ldr, .mpd, .dat) to PNG images with multiple stitched views, letting you visually inspect LEGO builds before sharing or reviewing them.

Instructions

Render an LDraw model file (.ldr/.mpd/.dat) to a PNG image.

Views are rendered at each comma-separated azimuth (degrees) and stitched side by side. Higher samples = cleaner but slower. Bounds: resolution 32..2048 px per view, samples 1..1024, 1..8 azimuths, and resolution^2 x samples x views at most 2**27. A referenced file the LDraw library lacks is left out of the picture and named in a text block after the image.

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": {
      "path": "<path>"
    },
    "name": "render_ldraw_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
samplesNo
azimuthsNo-60,120
resolutionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that multiple azimuth views are stitched side by side, the quality/speed tradeoff of samples, hard limits including the resolution^2 x samples x views <= 2**27 compute budget, and the degradation behavior when a referenced part is missing (omitted and named in a text block after the image). It leaves out failure behavior for an unreadable or invalid file and any permission/prerequisite notes.

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?

Front-loaded with the one-line purpose, then behavior, then limits — a sensible order with almost no filler. The bounds sentence is dense but every clause is load-bearing; only the line breaks inside sentences slightly interrupt flow.

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 4-parameter renderer with no annotations and no output schema, the definition covers inputs, limits, stitching, and missing-part handling. The one real gap is what the caller receives — an inline image, a file path, or a URL — which an agent would need in order to chain the result.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must compensate, and it largely does: path gets accepted file types, azimuths gets units, comma-separated format and a 1..8 view cap, samples gets a 1..1024 range plus the cleaner-but-slower tradeoff, and resolution gets px-per-view semantics with a 32..2048 range. Defaults are not restated, which is acceptable since the schema already declares them.

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 specific verb (render) plus resource (LDraw model file) and explicitly names the accepted extensions (.ldr/.mpd/.dat) and output format (PNG). This is enough to separate it from render_ldraw_text and bill_of_materials without consulting any schema.

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?

Usage is only implied: you call it when you have an LDraw file you want visualized. There is no explicit when-to-use/when-not, and no mention of the sibling render_ldraw_text as an alternative for text output, so routing between the two renderers is left to inference.

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