Skip to main content
Glama
Sign In

Vibe-Coding Hardware & Autonomous PCB Physical Synthesis MCP Server

by io.github.calligraphysystems
OverviewDiscussionsAdmin

calligraphy_list_gallery_boards

List the 55 / 55 conquered open-source PCB benchmark boards (20/20 PCBench Tier T Frontier + 13/13 Tier D Torture + 22/22 Multi-ECAD — 100.0% routed, 0 native KiCad 9 copper DRC violations) and available 1-click sample demo IDs ('2l_rp2040', '2l_stickhub', '4l_carrier').

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_list_gallery_boards"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose useful substance: exact result counts (55 boards, tier breakdowns) and the literal demo IDs that will be returned, plus verification claims about routing and DRC. It says nothing about auth requirements, ordering, pagination, or whether the board list is static — gaps that matter for a gallery/list endpoint with zero annotation coverage.

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 sentence that leads with the verb and the returned collections. The tier-parenthetical is dense but every element in it describes actual return content rather than being filler, and there is no redundant restatement of the name.

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

Completeness5/5

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

For a zero-parameter list tool with no output schema, the description fully covers what comes back: the board catalog with counts and the concrete sample demo IDs. Nothing an agent needs in order to call this correctly is missing.

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 tool takes zero parameters, so there is no parameter semantics to explain; baseline 4 applies. Schema coverage is reported at 100% with an empty properties object, so nothing is left undocumented.

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 opens with a specific verb and resource: 'List the ... PCB benchmark boards ... and available 1-click sample demo IDs'. The two returned collections are named concretely, and the enumerated demo IDs make the resource set unambiguous. It stops short of naming which sibling to use instead (e.g. compile/route), so it is clear but not sibling-differentiating.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use statement, no exclusions, and no pointer to a sibling tool. An agent can infer that sample demo IDs are meant to be fed into a downstream compile or route call, but that inference is entirely unstated.

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

All Vibe-Coding Hardware & Autonomous PCB Physical Synthesis MCP Server toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources