Skip to main content
Glama

List Verified 0-DRC Benchmark Gallery Boards

calligraphy_list_gallery_boards
Read-onlyIdempotent

Lists 13 fully routed open-source PCB benchmark boards with zero native KiCad copper DRC violations and returns 1-click sample demo IDs for quick routing tests.

Instructions

List the 13 conquered open-source PCB benchmark boards (100.0% routed, 0 native KiCad 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 observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare read-only, idempotent and non-destructive behavior, so the safety profile is covered. The description adds real value beyond that: a fixed cardinality of 13, the verification criteria (100.0% routed, 0 native KiCad copper DRC violations), and concrete demo ID values. It does not describe the item shape returned, but the list is small and bounded.

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 front-loaded sentence with the verb first; the parenthetical quality metrics and example IDs both carry information. Slightly dense with embedded parentheticals, but nothing is redundant or padded.

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, read-only listing with no output schema, the definition supplies enough: what is listed, how many, why they qualify, and example IDs. Lacking an output schema, it could say a bit more about what each entry contains, but an agent has what it needs to decide to call it.

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 schema has zero parameters, so there is no parameter semantics to explain; baseline is 4. The description usefully clarifies that the listed demo IDs are the kind of values a caller would feed into other tools rather than inputs to this one.

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?

States a specific verb ('List') and a concrete resource: the 13 open-source PCB benchmark boards plus 1-click sample demo IDs. The specific card counts ('2l_rp2040', '2l_stickhub', '4l_carrier') make it recognizable. It stops short of explicitly naming how it differs from discovery-adjacent siblings like calligraphy_compile_board or analyze_kicad_pcb.

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: an agent can infer this is the entry point for picking a board or demo ID before compiling/routing. There is no explicit 'use this when…' statement, no exclusions, and no named alternative for other board-discovery needs.

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