DatasheetVend

Extract power domains and consumption

datasheetvend_extract_power_domains

Read-onlyIdempotent

Extract power supply domains (VDD/VDDA/VBAT), low-power/sleep modes and their consumption, and battery-backup configuration. 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

Name	Required	Description	Default
`partName`	No	Optional part number / MPN to disambiguate a multi-part datasheet.
`documentPath`	Yes	https:// 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

Name	Required	Description
`engine`	No	Which engine produced this result
`review`	Yes
`status`	Yes	The module's completion status (for example approved, approved_with_warnings or empty), or FAILED when Fast Extraction could not extract the module
`contract`	Yes	Contract id, e.g. thermal_evidence_v2
`warnings`	Yes	Public engineering warnings from the extraction.
`module_id`	Yes	Canonical module id
`extracted_data`	Yes	The 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_output`	Yes	The module's canonical (CAD-ready normalized) output block.
`engineering_summary`	Yes	Concise human-readable engineering summary, when emitted.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 30, 2026

TDQS

A4/5.0

Behavior5/5

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

Annotations cover only the safety profile, and the description adds substantial behavior beyond them: the engine name is returned on every result, a failed Fast Extraction triggers a slower 'monolith_rescue' re-run that is still billed, the call can take several minutes requiring a 10-minute client timeout, and FAILED status only occurs after both engines fail. This is exactly the cost/latency/fallback information an agent cannot get from structured fields.

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?

Three dense sentences, front-loaded with the extracted content before the engine/latency details. Every sentence carries operational information, though the engine-rescue passage is long enough that a short bulleted structure would have been easier to scan.

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 needn't be explained, and the description still covers the two things an agent most needs: the engine field on results and the failure/timeout semantics. Nothing required to invoke or interpret the call correctly 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 description coverage is 100%, and the schema itself explains partName disambiguation and the https-only documentPath restriction. The description adds no parameter-level detail, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb ('Extract') and enumerates the exact resource set: power domains (VDD/VDDA/VBAT), low-power/sleep modes with consumption, and battery-backup configuration. That field list is clearly distinct from siblings like extract_thermal_limits or extract_absolute_max, though it never explicitly names an alternative tool to contrast against.

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

Usage Guidelines3/5

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

It documents the operational flow (Fast Extraction, fallback to deep engine, 10-minute client timeout) but gives no guidance on when an agent should choose this tool versus a related sibling such as build_component_twin or extract_peripheral_matrix. Usage context is implied by the extracted content rather than stated.

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

All DatasheetVend tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?