Skip to main content
Glama

Check whether chips work together (draft wiring)

datasheetvend_check_parts_compatibility
Read-onlyIdempotent

Will these chips work together? Ask before you have a netlist. Reads ONLY the extraction jobs you pass (2-12, from your account; repeats are removed, and two runs of one part are one part), drafts a starting wiring from pin names the way the DatasheetVend Workbench does (one elected microcontroller wired to each device over I2C or SPI), runs the electrical rules on it and answers per pair. The answer rests on that DRAFT wiring, never on your schematic: basis is 'draft_wiring', and to audit a real board use datasheetvend_crosscheck_netlist. Never a bare 'yes': each pair is CONFLICT, NO CONFLICT FOUND (nothing the bench could check failed, not 'they work together') or NOT CHECKED, with checks_ran of checks_total and what is missing. Device-to-device pairs are never wired, so they stay NOT CHECKED; with no part proven a microcontroller nothing is wired at all; UART and CAN are never drafted. Read the pair counts (conflict_pairs, no_conflict_pairs, not_checked_pairs), verdict, rule_coverage and the assumed-value counts before you repeat an answer. Findings are capped, with their total. A job whose outputs are gone is refused. 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": {
      "job_ids": "<job_ids>"
    },
    "name": "datasheetvend_check_parts_compatibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idsYes2-12 extraction jobs in your account, one or more per part. Include each part's pinout and logic_levels runs.
protocolNoWhich bus the draft wires: AUTO (default) lets the bench choose per device, as the Workbench does.
system_voltage_vNoThe bench's supply rail. Default 3.3.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), yet the description adds substantial context beyond them: deterministic code execution, no model calls, no credit cost, API key requirement, refusal when outputs are gone, findings capped, and specific drafting limits (device-to-device pairs, UART/CAN never drafted). Very rich. Slightly short of a 5 only because the drafting heuristics are summarized rather than fully pinned down.

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-loads the core question and the DRAFT-wiring caveat effectively, and every clause carries functional weight. It is a dense single block that verges on run-on, which costs a point, but little is genuinely wasted.

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

Completeness5/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 compensates by naming the returned fields an agent must read (basis, verdict, conflict_pairs/no_conflict_pairs/not_checked_pairs, rule_coverage, checks_ran of checks_total, findings cap). For a complex multi-part electrical check this is complete enough to interpret results correctly.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema: job_ids are deduplicated ('two runs of one part are one part'), must include pinout and logic_levels runs, and only the passed jobs are read. It also reinforces protocol/voltage behavior ('UART and CAN are never drafted', bench supply rail).

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 ('Will these chips work together?', drafts a starting wiring, runs electrical rules, answers per pair) and explicitly distinguishes itself from datasheetvend_crosscheck_netlist ('to audit a real board use...'). An agent can tell exactly what this does and what it isn't without opening the schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use ('Ask before you have a netlist') and when-not/alternative ('The answer rests on that DRAFT wiring, never on your schematic... to audit a real board use datasheetvend_crosscheck_netlist'). The exclusion is unambiguous and routes the agent to the right sibling.

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