Skip to main content
Glama
pcb-agent-mcp

pcb-agent-mcp

schematic_propose

Proposes and validates batches of schematic edits against a project file before applying them, letting you review planned symbol, wire, and connection changes.

Instructions

...

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": {
      "path": "<path>",
      "operations": "<operations>"
    },
    "name": "schematic_propose"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes ...
optionsNo ...
operationsYes ...

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.43

TDQS

D1.3/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure, yet it is empty. It does not say whether proposing is side-effect free, whether a proposal must later be committed via schematic_apply, whether it validates or reviews, or what the operations array does.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

There is no content to be concise about; the single ellipsis placeholder conveys zero information and is not front-loaded with anything usable. This is under-specification rather than brevity.

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

Completeness1/5

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

For a tool with nested-object parameters, no output schema, no annotations, and a sibling apply step, the description should explain the propose/apply lifecycle and the shape of operations. None of that is present, leaving the definition contextually empty.

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%, so the three parameters (path, options, operations) are already documented in the schema and the baseline of 3 applies despite the description adding nothing. The description neither names the parameters nor explains the nested operations object, but the schema covers that ground.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is an empty placeholder (' ...'), so it never states what schematic_propose does. An agent cannot tell from this whether the tool proposes schematic edits, drafts a netlist, or stages changes for schematic_apply. Purpose is effectively missing.

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

Usage Guidelines1/5

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

No when-to-use or when-not-to-use guidance appears anywhere in the definition. There is no routing signal distinguishing this from board_propose, schematic_apply, or schematic_review, which is exactly what an agent needs for a propose/apply family.

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