Skip to main content
Glama

Compile & Route PCB in Cloud Enclave

calligraphy_compile_board

Compile PCB designs with 3D HDI synthesis, DFM fixes, and physics validation, then receive DRC telemetry, preview crops, a Stripe checkout link, and stablecoin payment instructions.

Instructions

Compile a PCB through Calligraphy EDA (3D HDI synthesis + Snowman teardrop pad fillets + Zero-VIPPO DFM surgery + 3D nodal G*V=I physics) and return 0-DRC telemetry, preview crops, a single clickable Stripe Checkout URL, and watch-only per-job USDT/USDC stablecoin payment instructions. 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_compile_board"
  }
}

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').
tos_acceptedNo
requested_skuNoroute_3d
rush_deliveryNo
customer_emailNoagent@customer.io
include_eco_passNo
retention_policyNoauto_purge_on_download
no_itar_certifiedNo
export_control_certifiedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations declare it non-read-only, non-idempotent, non-destructive and open-world, and the description adds substantial context the annotations do not carry: what is produced (telemetry, crops, a checkout URL, watch-only payment instructions), implying a billable, asynchronous compile-and-route job. It does not say whether jobs persist, how long artifacts live, or what happens on re-invocation, so it stops short of full behavioral disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded and the two-mode structure is easy to follow, but the opening sentence is a run-on stuffed with marketing jargon ('Zero-VIPPO DFM surgery', '3D nodal G*V=I physics') that costs tokens without helping an agent decide or call correctly. The second and third sentences are efficient and earn their place.

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?

With 13 optional parameters, no output schema and a billable, non-idempotent operation, the description does well to enumerate return artifacts, which it must since no output schema exists. It is nevertheless incomplete on cost/SKU selection, retention behavior, and the ITAR/export-control flags — the highest-stakes parameters in the schema get zero coverage.

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 only 31%, so the description must compensate, and it does explain the four data-input parameters and the two modes convincingly. However, seven parameters with real consequences — requested_sku (the pricing/scope enum), rush_delivery, customer_email, include_eco_pass, retention_policy, no_itar_certified, export_control_certified — receive no explanation in either the schema or the description, leaving the commercial and export-control surface opaque.

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 names a specific verb and resource ('Compile a PCB through Calligraphy EDA') and enumerates the concrete outputs (0-DRC telemetry, preview crops, Stripe Checkout URL, stablecoin payment instructions). It is clearly distinguishable from a plain analyzer, though it never names the closest sibling, calligraphy_route_pcb, so an agent must infer the boundary itself.

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?

Usage is unusually explicit for input routing: Mode A requires sample_id among three named values, Mode B requires either project_path (stdio) or pcb_text+filename / upload_b64 (HTTP). That is a real when-to-use decision tree. What is missing is guidance on when to call this versus siblings like calligraphy_route_pcb or calligraphy_preflight_audit.

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