Skip to main content
Glama

Check Datasheet Status

check_extraction_status
Read-onlyIdempotent

Check the extraction status of one or more parts. Free. Each entry includes the current extraction step, elapsed seconds, and document ID.

Use after prefetch_datasheets or after read_datasheet triggers a new extraction.

Recommended polling cadence: every 10-15 seconds. A datasheet nobody has read before usually takes 1-3 minutes (a large one 5 or more), so faster polling wastes calls. Keep polling while the status is 'resolving', 'queued', 'pending' or 'extracting'; stop once it is 'ready', 'failed', 'no_source' or 'unsupported'.

DATASHEET STATUS VALUES:

  • 'ready' — extracted and indexed; call read_datasheet, search_datasheets, or analyze_image.

  • 'extracting' / 'in_progress' / 'queued' / 'pending' — extraction running or scheduled. Poll check_extraction_status every 10-15s until 'ready' or 'failed'. A datasheet nobody has read before usually takes 1-3 minutes; a large one can take 5 or more.

  • 'resolving' — we're still looking for the datasheet's PDF (distributors, then a web search; under a minute a part, longer for a big batch). Not final: keep polling check_extraction_status.

  • 'not_extracted' — known part but datasheet hasn't been fetched yet. Trigger it via prefetch_datasheets (up to 20 parts) or by calling read_datasheet (auto-triggers on first read).

  • 'no_source' — the search for a public datasheet has finished and found none for this MPN. Check the part number (search_parts), or retry prefetch_datasheets later. Otherwise upload the PDF via request_datasheet_upload + confirm_datasheet_upload (see those tools). Org-uploaded datasheets are private to the org.

  • 'unsupported' — PDF exists but can't be extracted (scanned image-only, encrypted, or corrupted). Upload a clean text-based PDF via request_datasheet_upload to override.

  • 'failed' / 'error' — extraction errored. The response includes the error reason. Retry via prefetch_datasheets or escalate to support.

  • 'rejected' — input wasn't a real MPN (bare value like '100nF', description, or reference designator). Fix the input and re-call.

  • 'deduplicated' — another part in the family already has this datasheet; same content is returned under the primary MPN.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
part_numbersYes1-20 MPNs to check. Must be specific manufacturer part numbers, not values or descriptions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / part_numbers / description
      Previous value: -"List of MPNs to check (max 20)"New value: +"1-20 MPNs to check. Must be specific manufacturer part numbers, not values or descriptions."
  2. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.