Skip to main content
Glama

connect_pins

Destructive

Connects named pins in a model under a specified net name and rejects implicit shorts across nets so pin-to-pin wiring remains explicit.

Instructions

Connect named pins in the model, e.g. U1.P1.0 to D1.K. Rejects implicit shorts across nets.

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": {
      "project": "<project>",
      "expected_revision": "<expected_revision>",
      "name": "<name>",
      "pins": "<pins>"
    },
    "name": "connect_pins"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
pinsYes
projectYes
expected_revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the mutation risk is covered structurally. The description adds genuine value beyond that by disclosing a validation behavior ('rejects implicit shorts across nets'), which tells the agent calls can fail on electrical grounds. It says nothing about atomicity, what happens to existing connections, or the expected_revision concurrency check.

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?

Two short sentences, front-loaded with the action and immediately followed by a usage example, with no filler. The brevity is efficient, though it is achieved partly by omitting information the agent needs.

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

Completeness2/5

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

This is a destructive mutation with four required, entirely undocumented parameters and no output schema. The description leaves unanswered what 'name' designates, how expected_revision should be obtained, and whether the whole pin list is connected atomically or fails entirely — all material for a write tool of this shape.

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?

Schema description coverage is 0%, so the description must carry parameter meaning, and it only covers 'pins' — supplying the pin reference format (U1.P1.0, D1.K) that the bare string array schema lacks. The other three required parameters (project, expected_revision, name) get no explanation at all, including the non-obvious optimistic-concurrency semantics of expected_revision.

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 and resource ('Connect named pins in the model') and backs it with a concrete example (U1.P1.0 to D1.K), so an agent knows exactly what operation is performed. It does not distinguish this from plausible siblings such as circuit_edit or pcb_route, which keeps it from a 5.

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 statement of when to use this tool versus alternatives, nor any preconditions (project must exist, revision must be current). Usage is only implied by the verb 'Connect'. The 'rejects implicit shorts' line is a constraint, not routing guidance.

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