kompas3d

Overview Schema Source Related Servers Discussions Admin

blueprint_view

Reads local image files or PDF pages as images with optional cropping, enabling AI agents to inspect blueprints and technical drawings.

Instructions

Read local PNG/JPEG/TIFF/WebP or a PDF page (1-based) as an image.

Optional crop is normalized [left,top,right,bottom] in 0..1. Cropping before downsampling helps read small dimensions. Maximum returned dimension is 2400px. This renders input; interpretation/OCR is the MCP client's responsibility.

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": "blueprint_view"
  }
}

Input Schema

Name	Required	Description	Default
`crop`	No
`page`	No
`path`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 5, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the burden and does well: it explains crop normalization, recommends cropping before downsampling, caps output at 2400px, and explicitly states rendering only, with OCR/interpretation delegated to the client. No safety or failure behavior noted, but the tool is clearly a read operation by design.

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?

Four short sentences, each conveying a distinct fact: formats+page, crop format, resolution limit, rendering responsibility. No filler.

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 simple read/convert tool with no output schema, the description covers input formats, page selection, crop behavior, output size cap, and the limit of its responsibility. It is complete enough for an agent to invoke correctly, though it does not specify the image return format (e.g., base64/URL).

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 has 0% description coverage, so the description compensates: it explains `crop` as normalized [left,top,right,bottom] in 0..1 and notes `page` is 1-based; `path` is implied to be a local file path by 'Read local ...'. This adds real meaning beyond bare schema titles.

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 action 'Read' and exact resource types (PNG/JPEG/TIFF/WebP, PDF page), with 1-based page indexing and output-as-image. This differentiates it from sibling CAD/API tools, and the final note clarifies it only renders, not interprets.

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?

Provides clear context: use for reading local raster images or PDF pages as images. It does not name alternatives or exclusions, but the supported file types and rendering scope are unambiguous.

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