Part knowledge — giving firmware agents the datasheet
Category: Engineering
Ask a language model for the I²C slave address of a sensor and it will tell you. Ask it again, and it will guess, the datasheet lists four of them in one table and the model saw that table once, compressed into weights.
The address is a fact with a location: page 19 of a specific PDF, published by the manufacturer, revised on a date. An agent should be able to go and read it.
Why we stopped parsing datasheets
The obvious approach is to parse the PDFs into structured facts, walk the register tables, extract name, offset, reset value, store the result.
Unfortunately vendors do not share a table layout, so each datasheet needs its own grammar.
We extract parts text once, page by page, and let the calling model read the pages 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, then read.
Using it over MCP
Connect the hosted server (one line, registers whatever agents you have):
curl -fsSL https://labwired.com/mcp.sh | sh
Manual alternative: claude mcp add labwired --transport http https://api.labwired.com/mcp
Use labwired_datasheet to access parts knowledge!
