Calligraphy EDA MCP Server

List Verified 0-DRC Benchmark Gallery Boards

calligraphy_list_gallery_boards

Read-onlyIdempotent

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

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real value by disclosing the fixed size of the result set (55 boards), its tier composition, and that the boards are pre-verified with 100.0% routed / 0 native KiCad 9 copper DRC violations, which tells the agent the returned data is trusted and finite (no pagination concern for 55 items).

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 front-loaded sentence: the resource and scope come first, followed by the demo-ID payload. The tier arithmetic is dense but each number conveys selection-relevant information about result-set size and quality.

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

Completeness4/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 adequately signals what comes back (verified boards plus demo IDs with literal examples). It stops short of describing the shape of each board entry, which is the only remaining gap for a consumer that must parse the response.

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 nothing for the description to disambiguate; schema coverage is 100% and the baseline of 4 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 ("List") plus the resource (verified PCB benchmark gallery boards) and quantifies the scope as 55 boards with tier breakdowns. It also names the secondary payload, 1-click sample demo IDs with literal examples, so an agent can distinguish it from compile/route siblings at a glance.

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?

Usage is only implied: the mention of "1-click sample demo IDs" hints this is the entry point for obtaining board IDs to feed into compile/audit tools, but no explicit when-to-use or when-not-to-use guidance is given and no sibling is named as an alternative.

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

All Calligraphy EDA MCP Server tools Inspect

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

Need Help?