Skip to main content
Glama

Audit a KiCad netlist against extracted datasheets

datasheetvend_crosscheck_netlist
Read-onlyIdempotent

Audit a KiCad netlist against the datasheets your account has extracted with DatasheetVend. Compares symbol names with the datasheet, checks every pin exists, supply and ground pins sit on rails of the right kind and voltage, NC pins are left open, pin functions agree across each net, and pull-ups and the electrical rules that have data to run. verdict says how many pins were really compared and rule_coverage which rules could not run; a part with no matching extraction is reported as unmapped, never guessed. Deterministic: runs DatasheetVend's checks in code, calls no model and extracts nothing. Costs no credits. Needs a DatasheetVend API key.

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": {
      "netlist": "<netlist>",
      "job_ids": "<job_ids>"
    },
    "name": "datasheetvend_crosscheck_netlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idsYesExtraction jobs in your account to audit the netlist against (1-12), one or more per part.
netlistYesThe KiCad netlist as exported: the s-expression .net or the XML form (at most 2 MB).
system_voltage_vNoUsed only where no net name states a voltage. Default 3.3.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing that the audit is deterministic, calls no model, extracts nothing, and costs no credits, plus auth requirements. It also explains failure semantics ('a part with no matching extraction is reported as unmapped, never guessed') and what verdict and rule_coverage report, none of which the structured fields convey. Consistent with readOnlyHint/idempotentHint.

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?

Front-loaded with the audit action and its checks, followed by terse operational facts (deterministic, no credits, API key). Dense but every clause carries technical content; the check enumeration is long but functional rather than padding.

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 does the needed work by explaining verdict, rule_coverage, and unmapped-part reporting. Auth, cost, and determinism are covered; minor gaps remain around error behavior for malformed or oversized netlists, though the size limit is in the schema.

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 coverage is 100%, so parameters (job_ids, netlist, system_voltage_v) are already documented at the field level. The description adds only indirect meaning, hinting at voltage-rail checking that motivates system_voltage_v, without explaining its fallback behavior beyond what the schema states.

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 and resource ('Audit a KiCad netlist against the datasheets your account has extracted') and enumerates the concrete checks performed (symbol names, pin existence, rail voltage, NC pins, pin functions, pull-ups, ERC). This clearly separates it from extraction siblings like datasheetvend_extract_pinout or datasheetvend_build_component_twin.

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

Usage Guidelines4/5

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

It establishes the prerequisite that job_ids must be extraction jobs already in the account and notes a DatasheetVend API key is required. It does not explicitly name an alternative tool or a when-not-to-use condition, so guidance is clear contextually but not a full routing statement.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources