Part knowledge gives firmware agents the datasheet
Category: Engineering
Ask a language model for the I²C slave address of a sensor. The model gives you an address. Ask the same question again. The model guesses. The datasheet lists four addresses in one table. The model saw that table one time and stored the table as weights.
The address is a fact with a location. The location is page 19 of one PDF. The manufacturer published that PDF and revised the PDF on a date. An agent must be able to read that page.
Why we stopped the datasheet parse
The obvious approach parses each PDF into structured facts. The parser reads each row of the register tables. The parser extracts the name, the offset, and the reset value. The parser then stores the result.
Vendors do not share one table layout. Each datasheet needs its own grammar.
We extract the part text one time, page by page. The model that sends the request reads the pages that it needs.
flowchart LR
A["`Agent needs a fact
(address, opcode, timing)`"] -- search --> B["`BM25 over
page text`"]
B -- "top pages, full text" --> C["`Agent reads
and extracts`"]
C -- "cite page + sha256" --> D["`Citation that
still resolves later`"]
Caption: Search first. Read the text next.
Part knowledge through MCP
Connect the hosted server with one line. The line registers the agents that you have.
curl -fsSL https://labwired.com/mcp.sh | sh
The manual command is claude mcp add labwired --transport http https://api.labwired.com/mcp.
Use labwired_datasheet to access part knowledge.
