Skip to main content
Glama

Run Pre-Flight CAD Doctor & Instant Tier Quote

calligraphy_preflight_audit
Read-onlyIdempotent

Inspect .kicad_pcb files or .zip project bundles to verify outline and pad readiness, then return a deterministic 3-Lever NRE-anchored price quote.

Instructions

Inspect a .kicad_pcb file or .zip project bundle (including atopile/tscircuit/Altium/Allegro builds), verify outline/pad readiness, and return a deterministic 3-Lever NRE-anchored price quote ($149 vibe_micro for <=150 pads up to $1,495+ route_3d). Mode A (Zero-File Demo): Pass sample_id='2l_rp2040' (or '2l_stickhub', '4l_carrier'). Mode B (User's Local Board): Pass a local file path in project_path (stdio mode) or pass its contents in pcb_text + filename (or upload_b64 for .PcbDoc/.zip).

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

Input Schema

NameRequiredDescriptionDefault
filenameNoboard.kicad_pcb
pcb_textNoRaw CAD file contents (.kicad_pcb, .dsn, .ato, .tsx, .xml) for remote HTTP MCP calls
sample_idNoOptional built-in sample board ID ('2l_rp2040', '2l_stickhub', '4l_carrier')
upload_b64NoBase64-encoded CAD file or .zip bundle for remote HTTP MCP calls
project_pathNoLocal stdio CLI path or built-in sample ID ('2l_rp2040', '2l_stickhub', '4l_carrier').
requested_skuNoroute_3d
rush_deliveryNo+35% Instant <45m Enclave Rush Turnaround
customer_emailNoEngineer email for 30-day ECO license matchingagent@customer.io
include_eco_passNo+50% 30-Day Unlimited ECO Re-Spin Pass

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, and open-world behavior. The description adds that the quote is deterministic and NRE-anchored, gives the price span and demo sample IDs, and clarifies supported build formats and input channels; it omits auth, rate-limit, and full return-shape details.

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?

The description is front-loaded with inspect/verify/quote, then pricing and the two modes, so it is easy to scan despite being dense. Some promotional pricing detail and jargon like '3-Lever NRE-anchored' could be tightened, but nothing major is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex 9-parameter CAD-audit-plus-quote tool with no output schema, the description explains input modes and supported formats but not the audit output or quote structure, error cases, or full SKU semantics. The annotations cover safety well, so the main remaining gap is output and enum completeness.

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 coverage is 78%, so most parameters are documented by the schema. The description adds useful cross-parameter meaning: sample_id selects the zero-file demo, project_path is the stdio local path, pcb_text+filename or upload_b64 are remote alternatives, and accepted file types are listed. It does not explain all requested_sku enum values or the filename default, so it is not a 5.

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?

The description gives a specific verb and resources: inspect a .kicad_pcb/.zip, verify outline/pad readiness, and return an NRE-anchored price quote. It clearly distinguishes demo vs local-board modes, but it does not explicitly differentiate itself from likely siblings such as audit_pcb_dfm_rules or analyze_kicad_pcb.

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?

It explicitly routes Mode A to sample_id and Mode B to project_path in stdio or pcb_text+filename/upload_b64 for remote calls, which is clear invocation guidance. It does not state when not to use this tool or point to a sibling for DFM-only checks, so it stops short of a 5.

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