Skip to main content
Glama

Extract on-chip peripheral matrix

datasheetvend_extract_peripheral_matrix
Read-onlyIdempotent

Extract the on-chip peripheral inventory, one row per instance, in 13 classes: serial/communication (UART/USART, SPI, I2C, CAN, USB, Ethernet, SDIO, I2S/SAI), analog blocks (ADC, DAC, comparator, op-amp, voltage reference, temperature sensor), timers and watchdogs, DMA, security/math accelerators (crypto, RNG, CRC), external memory interfaces (FMC/FSMC/EMC, memory-mapped QSPI), display/camera/touch, interrupt controllers, GPIO, clock/reset, low-power modes, debug/trace and device identity. Each row carries the datasheet page it was read from, where one was recorded. For ADC/DAC/comparator electrical specs (resolution, sampling rate, INL/DNL, propagation delay) use datasheetvend_extract_analog_specs. For per-mode current draw, wakeup timing, and reset/brown-out threshold voltages use datasheetvend_extract_power_domains. Runs DatasheetVend Fast Extraction: a page scout routes targeted model reads and the module's own deterministic readers, then the same normalization and completion checks as a dashboard job finish the result, usually in seconds; engine names the engine on every result. If Fast Extraction cannot complete the module, the slower deep engine re-runs that module alone (engine.runtime is then monolith_rescue; the result says so, and it is billed as delivered). A rescue can take several minutes, so set a client timeout of 10 minutes. Only if the deep engine also cannot deliver does the module return status FAILED with the reason.

Input Schema

NameRequiredDescriptionDefault
partNameNoOptional part number / MPN to disambiguate a multi-part datasheet.
documentPathYeshttps:// URL to the datasheet PDF. The remote /api/mcp endpoint accepts ONLY https:// URLs (it downloads them); a local filesystem path works solely in local stdio mode (npm run mcp:serve).

Output Schema

NameRequiredDescriptionDefault
engineNoWhich engine produced this result
reviewYes
statusYesThe module's completion status (for example approved, approved_with_warnings or empty), or FAILED when Fast Extraction could not extract the module
contractYesContract id, e.g. thermal_evidence_v2
warningsYesPublic engineering warnings from the extraction.
module_idYesCanonical module id
extracted_dataYesThe module's extraction after its own normalization — values with the datasheet page they came from (source_page, where one was recorded) and, where the module provides them, confidence_score and source_text_snippet.
canonical_outputYesThe module's canonical (CAD-ready normalized) output block.
engineering_summaryYesConcise human-readable engineering summary, when emitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations cover read-only/idempotent/open-world, and the description adds genuinely non-derivable behavior: a Fast Extraction pipeline with page-scout routing, an `engine` field on every result, an automatic monolith_rescue fallback that is slower and billed as delivered, a recommended 10-minute client timeout, and FAILED status only after both engines fail. That is exactly the operational context annotations cannot carry.

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 verb and resource, then the class inventory, then routing, then runtime semantics. The 13-class enumeration is long but earns its place by defining scope; the pipeline paragraph is slightly verbose but conveys fallback and timeout facts the agent needs.

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 an output schema present, return values need no explanation, and the description still covers scope, exclusions, latency expectations, fallback behavior, and failure signaling. Nothing an agent needs in order to call this correctly and set an appropriate timeout is missing.

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% and both parameters (documentPath, partName) are fully documented in the schema, including the https-only constraint for the remote endpoint. The description adds no parameter-level detail of its own, so baseline 3 applies.

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+resource ('Extract the on-chip peripheral inventory, one row per instance') and enumerates the 13 covered classes, so the agent knows exactly what comes back. It also names the sibling tools that handle adjacent data (analog_specs, power_domains), so the boundary is unambiguous.

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?

Explicitly routes the two likely-confused cases elsewhere: ADC/DAC/comparator electrical specs to datasheetvend_extract_analog_specs, and per-mode current / wakeup timing / reset thresholds to datasheetvend_extract_power_domains. Every exclusion names the condition that selects the alternative.

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