DatasheetVend

Extract AC timing characteristics

datasheetvend_extract_timing_characteristics

Read-onlyIdempotent

Extract AC timing: setup/hold (tSU, tH), propagation delays, maximum clock frequencies (fMAX), rise/fall times, and bus timing. 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.4/5.0

Behavior5/5

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

Annotations only cover safety (readOnly/idempotent/openWorld), while the description discloses what actually happens: a page scout routing targeted model reads, deterministic readers, engine naming on every result, a slower 'monolith_rescue' engine fallback that is billed as delivered, a recommended 10-minute client timeout, and FAILED status with a reason. This 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 extracted field list, then the operational caveats. The engine/rescue/timeout material is long and somewhat dense, but each clause carries actionable information (timeout, failure mode, billing); it is not padding.

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, the description need not explain return structure; it instead covers what remains unknown — runtime engine identity, rescue timing risk, and terminal FAILED behavior. Nothing an agent needs before calling 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 are already well documented in-schema (including the https-only constraint of the remote endpoint). The description adds no parameter detail beyond the schema, so the 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 and resource ('Extract AC timing') and enumerates the exact quantities produced (tSU/tH, propagation delays, fMAX, rise/fall, bus timing). That field list cleanly separates it from siblings such as extract_absolute_max, extract_analog_specs and extract_logic_levels.

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

Usage Guidelines4/5

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

The enumerated AC parameters make the selection context clear versus DC/absolute-max/analog siblings, and it explains the extraction path taken. It never explicitly names alternatives or says when NOT to use it, so it falls short of a 5.

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?