Skip to main content
Glama

Synthesize & Route Multi-Layer PCB

calligraphy_route_pcb

Route and synthesize PCBs from built-in samples or local CAD files to zero opens and zero DRC, returning Stripe, Coinbase Pay, and USDT/USDC payment instructions.

Instructions

Alias for calligraphy_compile_board: synthesize and route a PCB through Calligraphy EDA (0 opens, 0 DRC) and return Stripe, Coinbase Pay (x402), and watch-only USDT/USDC 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_route_pcb"
  }
}

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
customer_emailNoagent@customer.io

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations' non-read-only, open-world, non-idempotent profile, the description identifies external EDA processing, a claimed zero-open/zero-DRC outcome, and Stripe, Coinbase Pay, and stablecoin payment instructions as returned behavior. It still leaves unclear whether a persistent job is created, whether payment is required before processing, and how results are subsequently retrieved.

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 the alias and core operation, then organized into two clearly labeled input modes with concrete values. It is somewhat dense, and the unexplained shorthand '(0 opens, 0 DRC)' plus the long payment-method list reduce immediate readability.

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 seven-parameter remote EDA and payment tool without an output schema, it adequately covers the main purpose, calling patterns, and high-level outputs. Important gaps remain around SKU selection, customer_email usage, authorization or payment prerequisites, synchronous versus asynchronous behavior, and what PCB artifacts or job identifiers are returned.

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 mode guidance adds useful relationships among sample_id, project_path, pcb_text plus filename, and upload_b64, explaining how board source and transport determine the input combination. However, requested_sku and customer_email receive no semantic explanation, and the upload_b64 guidance only partially clarifies applicable formats.

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?

The description states the specific action and resource—synthesizing and routing a PCB through Calligraphy EDA—and identifies the tool as an alias for the sibling calligraphy_compile_board. It also distinguishes the expected result with the zero-open/zero-DRC claim and names the payment-instruction outputs.

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?

Modes A and B give explicit invocation contexts: a zero-file sample demo versus a user's board, with further guidance for local stdio paths, remote text uploads, and base64 uploads. It does not explain when this compilation workflow should be used instead of preflight, analysis, or other siblings, but an alias needs little differentiation from calligraphy_compile_board itself.

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