Skip to main content
Glama

check_symbol_fields

Check Value, MPN and confirmation fields of schematic symbols against BOM variants; report conflicts, unconfirmed entries, old-convention moves and missing parts.

Instructions

Check the MPNs of the symbols: the fields Value, MPN, Value_Confirmed and MPN_Confirmed.

Use this tool only when the MCP server datasheet-lens is not available: its tool project_check does the same check, and also checks the datasheets. The two tools give the same messages (a datasheet-lens with the model of the four fields, of 2026-11-07 or later: an older one reads the MPNs from the parentheses of Value).

The convention: Value holds the general value ("2N7002", "100nF 10V"), the field MPN the MPNs, the fitted part first ("2N7002LT1G, BSS138LT1G"; the separators are "," and ";", an MPN with "," or ";" is in quotes, as in CSV), and the hidden fields Value_Confirmed and MPN_Confirmed the copies of the last confirmation. A symbol with the MPNs in the parentheses of Value (the old convention) gets the move into the field MPN.

The tool reads the BOM of kicad-cli (also the DNP symbols: the user can fit them at any time) of the default variant and of each variant (KiCad 10). For each symbol it gives the conflicts, the changes that the user must confirm, the symbols that are not confirmed, the moves of the old convention, and the symbols with no part. Each message gives the change for set_symbol_fields. Write the fields only after the user confirmed them.

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": {
      "schematic_path": "<schematic_path>"
    },
    "name": "check_symbol_fields"
  }
}

Input Schema

NameRequiredDescriptionDefault
schematic_pathYesA .kicad_sch file of the project. The tool checks the full project.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that the tool reads the kicad-cli BOM including DNP symbols, covers the default variant and each variant (KiCad 10), and produces conflict/change/unconfirmed/move/no-part messages without writing anything. It loses a point for the garbled parenthetical about datasheet-lens versions ("a datasheet-lens with the model of the four fields, of 2026-11-07 or later") and for never stating plainly that the tool is read-only.

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

Conciseness3/5

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

The purpose and the usage gate are front-loaded and earn their place, but the middle section sprawls into long run-on sentences with nested parentheses and a fragment ("a datasheet-lens with the model of the four fields, of 2026-11-07 or later"). The MPN convention paragraph is genuinely useful for interpreting messages, but it is dense and could be tightened considerably.

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?

For a project-wide, multi-variant BOM check this covers the essentials: scope, variant handling, DNP inclusion, the categories of message returned, and the confirm-before-write workflow. An output schema exists so return values need not be spelled out, and the remaining gap (report format, performance on large projects) is minor.

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?

There is a single parameter with 100% schema description coverage, so the schema already explains schematic_path and that the whole project is checked — the description's "of the project" adds nothing new. Baseline 3 applies; the description does not compensate with any path or variant syntax detail.

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?

Opens with a specific verb and resource: "Check the MPNs of the symbols" and enumerates the four fields inspected (Value, MPN, Value_Confirmed, MPN_Confirmed). It also implicitly separates itself from the write-side sibling set_symbol_fields, so an agent can tell check from fix without opening a 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 an explicit gate: "Use this tool only when the MCP server datasheet-lens is not available", names the preferred alternative (project_check) and explains why it is preferred. It also closes the loop with the next step — confirm with the user, then write via set_symbol_fields — which is exactly the routing an agent needs.

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