Skip to main content
Glama

pcb_read

Read-only

Read the current ARES PCB layout to retrieve nets, layers, board outline, rules, copper paths, and calibrated through-via details for inspection or analysis; simulation must be stopped.

Instructions

Export and read the CURRENT owned ARES PCB: native pad indices, nets, layers, board outline, rules, copper paths and calibrated through-vias including native drill/style/span. Stopped simulation required. Returns revision token; pad indices are NOT schematic physical pin numbers.

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": {
      "session": "<session>"
    },
    "name": "pcb_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish readOnly/non-destructive/closed-world, and the description adds real behavioral context on top: a state precondition (simulation must be stopped), a side-effect-relevant return value (revision token), and an important semantic caveat that pad indices are not schematic physical pin numbers. It does not discuss cost, size, or what happens if the simulation is running.

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?

Three tightly packed sentences with the resource scope and payload front-loaded, then the precondition, then the return/caveat. No filler or restated title.

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?

With no output schema, the description usefully compensates by enumerating the returned data and calling out the revision token, and it flags the simulation-stopped requirement. The remaining gap is the undocumented 'session' parameter, which leaves a required input ambiguous.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is a single required parameter, 'session', with 0% schema description coverage, and the description never mentions it — no explanation of whether it is a session id, where it comes from, or what happens with a stale value. With coverage this low the description is expected to compensate and does not.

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 gives a specific verb ('Export and read') and a precisely scoped resource ('the CURRENT owned ARES PCB'), then enumerates what is returned: pad indices, nets, layers, board outline, rules, copper paths and through-vias. The qualifier 'CURRENT owned' implicitly separates it from live_read/native_read/project_read reads, but no sibling is named, so differentiation requires inference.

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 context is only implied through the precondition 'Stopped simulation required', which tells the agent when the call is valid. There is no statement of when to choose this over native_read, live_read or project_read, and no exclusion guidance.

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