Skip to main content
Glama
cadcraft-electrical-mcp

cadcraft-electrical-mcp

sheet_preview

Render a specific CAD sheet by 1-based page number to PNG and return the image for inspection.

Instructions

Render one sheet (1-based page number) to PNG with CADCraft and return the image to inspect.

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": {
      "number": "<number>"
    },
    "name": "sheet_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
numberYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations declare non-read-only, non-idempotent, open-world, non-destructive behavior, and the description adds useful context: it is executed via CADCraft and returns image data rather than metadata. It does not disclose what side effect makes it non-read-only (a rendered file?), nor failure handling for an invalid page number.

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?

A single front-loaded sentence with the action, the scope, the format, and the return value; nothing is wasted or padded.

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 one-parameter tool with no output schema, this covers action, indexing convention, engine, and return type. Only error conditions and the nature of the write side effect are absent, which are minor for a preview tool.

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?

The schema names the only parameter just 'Number' with 0% coverage, so the description carries the burden and does: it specifies 'one sheet' (not a range) and '1-based page number' indexing, which is exactly the disambiguation an agent needs. It does not cover out-of-range behavior, but the core semantic is supplied.

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?

States a specific verb (render), a specific resource (one sheet), the target format (PNG), the engine (CADCraft), and the return payload (image to inspect). That clearly separates it from sibling readers like sheet_get, though no sibling is named explicitly.

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 by the phrase 'return the image to inspect', which suggests visual verification; there is no statement of when to prefer this over sheet_get or other sheet tools. Adequate but leaves the agent to infer the choice.

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