Skip to main content
Glama
Sign In
vibe-hardware-mcp

vibe-hardware-mcp

by calligraphysystems
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

calligraphy_download_fab_bundle

Download unlocked routed .kicad_pcb files plus a turnkey JLCPCB/PCBWay .zip bundle containing Gerbers, drills, BOM, CPL, and a 3D viewer after payment or license verification.

Instructions

Download the unlocked routed .kicad_pcb and turnkey JLCPCB/PCBWay .zip bundle (Gerbers, Excellon drills, IPC-D-356, BOM, CPL, and 3D HTML5 viewer) once paid via Stripe Checkout, autonomous USDT/USDC stablecoin verification, or active 30-day board license.

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": {
      "job_id": "<job_id>"
    },
    "name": "calligraphy_download_fab_bundle"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesJob ID returned by calligraphy_compile_board
output_dirNoLocal directory to save unlocked files (stdio CLI mode)
include_bundle_b64NoSet True over remote HTTP to inline the base64 .zip bytes and trigger auto-purge immediately; defaults to False so the returned download_zip_url remains active for browser/curl download.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the key behavioral trait: the call is payment/license-gated, and 'unlocked' implies otherwise-locked artifacts. It stops short of saying what happens on an unpaid call (error vs. redacted output) or whether repeated downloads are permitted under a license, leaving some gaps for a no-annotation tool.

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?

A single sentence, front-loaded with the verb and deliverables before the gating clause, with no filler. It is dense and somewhat run-on with the long parenthetical list, but every clause contributes information.

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?

There is no output schema and no annotations, so the description should ideally cover the return shape, yet download_zip_url and the base64 alternative are only surfaced indirectly through the schema's include_bundle_b64 text. Payment gating and bundle contents are covered, but the response contract and failure behavior remain unstated.

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 100%, with job_id, output_dir, and include_bundle_b64 all documented in the schema including the auto-purge tradeoff. The description adds no parameter-level meaning of its own, so the baseline 3 applies.

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 verb (download) plus the exact artifacts returned: the unlocked routed .kicad_pcb and a turnkey JLCPCB/PCBWay .zip with enumerated contents (Gerbers, Excellon, IPC-D-356, BOM, CPL, 3D viewer). This clearly distinguishes it from siblings like calligraphy_compile_board, calligraphy_route_pcb, and calligraphy_get_job_status.

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?

It gives a real precondition ('once paid via Stripe Checkout, autonomous USDT/USDC stablecoin verification, or active 30-day board license'), which tells the agent this is a gated post-payment step. It does not, however, point to the sibling that establishes that state (e.g., calligraphy_get_job_status or calligraphy_verify_stablecoin_payment) or state what to do when payment is not yet confirmed.

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

Deploy Server

Other Tools